Origin: Cannot create storage

Created on 14 May 2017  Â·  27Comments  Â·  Source: openshift/origin

Hello,

after fresh installation, when I'm trying to create new storage from web console I'm always gets the error message: no persistent volumes available for this claim and no storage class is set, reason: Failed binding

Version

openshift v1.5.0+031cbe4
kubernetes v1.5.2+43a9be4
etcd 3.1.0

Steps To Reproduce
  1. Go to the web console Storage section
  2. Push on Create Storage button
  3. Create storage.

The generated YAML config is

apiVersion: v1
kind: PersistentVolumeClaim
metadata:
  name: storagename
  namespace: gitlab-infrastructure
  selfLink: /api/v1/namespaces/example/persistentvolumeclaims/storagename
  uid: 2827819d-389a-11e7-95f3-4e4829be6605
  resourceVersion: '6296'
  creationTimestamp: '2017-05-14T11:40:40Z'
spec:
  accessModes:
    - ReadWriteOnce
  resources:
    requests:
      storage: 1Gi
status:
  phase: Pending
Current Result

This storage always has Pending status and in Monitoring->Events I receive error message no persistent volumes available for this claim and no storage class is set.

Please help me what am I doing wrong? I am a newcomer in Openshift.

componenstorage kinquestion lifecyclrotten prioritP2

Most helpful comment

I am having same issue.

Anyone can help us?

All 27 comments

I am having same issue.

Anyone can help us?

Same here...

Any update here? Facing same issue in a v3.6 cluster

@romantomchak Did you get a chance to resolve this issue??

Looks like cluster does not have any persistent volumes. You should create PVs first.

Thanks @debianmaster

After adding openshift_cloudprovider_kind=gce in inventory/hosts file did the trick. Now Openshift is able to create PV dynamically on GCE without any extra config.

Awesome. Good luck.

On Sun, Sep 24, 2017 at 2:04 AM Tapas Jena notifications@github.com wrote:

Thanks @debianmaster https://github.com/debianmaster

After adding openshift_cloudprovider_kind=gce in inventory/hosts file did
the trick. Now Openshift is able to create PV dynamically on GCE without
any extra config.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/openshift/origin/issues/14184#issuecomment-331697149,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABX1wfN37dYRG29hFe8_WsiVaSotfUO6ks5slhsngaJpZM4NaW6M
.

Cannot create persistent volume claim "mysql". persistentvolumeclaims "mysql" is forbidden: exceeded quota: 6170702e726f6d616e79736f667440676d61696c2e636f6d-noncompute, requested: requests.storage=1Gi, used: requests.storage=0, limited: requests.storage=0.

@lauer3912 You have to increase your Quota limit by adding payment method to Google account

@tapas4java Where to increase the quota? I can not find ah

@tapas4java where exactly can i set that config? I experience the same issue as @romantomchak , cannot create pvc's.

Hope you are following Jennings's Video ??

I have added openshift_cloudprovider_kind=gce to inventory/hosts file

I am not on GCE. I wanted to create a PVC locally on my mashine.

any process on it.

Hi Folks,

afaik you cannot use persistent volumes when you haven't configured an appropriate provider before.

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

same here

anyone found a fix for this?

@rohilshah95 @japplewhite do you have persistent storage configure to openshift? else you will see this issue. Also make sure you have a default storageclass

oc get pv or . oc get storageclass . should show you

i hit the same issue. we have openshift 3.9 with kubernetes 1.9 ? we dont have any GCE as this cluster is on-premise ...do i have to create NFS PV first to consume PVC ? i thought PV should work local disk as well.

can someone help what is the solution.

@rushins
you should have a PV first or a storage class to create a PVC.

use oc get pv . and oc get storageclass to see if you
have any

On Wed, Jul 25, 2018 at 3:38 AM rushins notifications@github.com wrote:

i hit the same issue. we have openshift 3.9 with kubernetes 1.9 ? we dont
have any GCE as this cluster is on-premise ...do i have to create NFS PV
first to consume PVC ? i thought PV should work local disk as well.

can someone help what is the solution.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/openshift/origin/issues/14184#issuecomment-407526619,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABX1wa4zMxMmCq2ASkNPVTcFnS9NuitQks5uJ3engaJpZM4NaW6M
.

so as stated before "do i have to create NFS PV first to consume PVC " i created PV and rest is fine, however i was under impression that Openshift Contianer Platform will allow to use localhost path based disk as PV ? if this is possible in redhat openshift container platform? as other kubernetes without redhat openshift is doable with this way using localhost path LVM devices. ?

Openshift is k8s , if you can do it in k8s then you can do in origin/ocp

On Fri, 27 Jul 2018, 22:22 rushins, notifications@github.com wrote:

so as stated before "do i have to create NFS PV first to consume PVC " i
created PV and rest is fine, however i was under impression that Openshift
Contianer Platform will allow to use localhost path based disk as PV ? if
this is possible in redhat openshift container platform? as other
kubernetes without redhat openshift is doable with this way using localhost
path LVM devices. ?

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/openshift/origin/issues/14184#issuecomment-408433662,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABX1wXMHvoTQ_SvdeuHuqQ0iCVywQMUwks5uKyJDgaJpZM4NaW6M
.

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

Was this page helpful?
0 / 5 - 0 ratings