Description of problem: Creating a new pvc using cinder storageclass results in the pvc being stuck in a pending state. restart openshift services on masters ( systemctl restart atomic-openshift-*) resolves the issue temporarily and the volume is created in the cinder backend. After some time the pvc is stuck pending again until we restart services. Version-Release number of selected component (if applicable): contianerised install of OCP 3.6 (v3.6.173.0.5-5) How reproducible: Always Steps to Reproduce: 1. Creating a new pvc using cinder storageclass 2. 3. Actual results: pvc being stuck in a pending state. Expected results: Volume to be created in the cinder backend. Error: "failed to provision volume for claim test/pv0001-claim with StorageClass cinder. No suitable endpoint could be found in the service catalog." Additional info: Seems to be similar to: https://github.com/openshift/origin/issues/15979 Workaround seems to be re-configured the cloudprovider openstack.conf to use keystone v2.0 with a local OpenStack user. Same workaround was mentioned in another bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1490768 - Bug 1490768 - Failed to provision cinder volume, got http response code 300
Please, will you provide cloud.conf configuration file. Will you, please, also provide OpenStack service catalog, especially the Cinder entries.
Verified this bug in OCP3.7 on our openstack openshift v3.7.0-0.189.0 kubernetes v1.7.6+a08f5eeb62 After reauth, PVC can be created successfully and get into "Bound" phase. So marked this bug as verified.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2017:3188
Note: Backport to 3.6 provided in 1527973.