Red Hat Bugzilla – Bug 1473770
Cinder volume not attaching to the Pod
Last modified: 2017-11-28 17:05:05 EST
Description of problem:
Cinder volume gets attached to a kubernetes worker node but not to a pod.
This bug is already fixed upstream.
This Red Hat internal bug is to track the issue and ensure we consume the upstream fix.
Version-Release number of selected component (if applicable):
OCP 3.5, RHEL 7.3, OSP 9 (Mitaka)
Steps to Reproduce:
Use openstack as a cloud provider and create a pod with Cinder backed volume - either using a PersistentVolumeClaim or directly in a pod definition.
After manually detaching Cinder volume from an Openstack instance, it get's attached again and the error repeats.
Cinder volume gets mounted to a pod and pod goes to a 'Running' state
This is the upstream bug report and workaround:
This is the upstream fix:
This is a related bug but not the same issue:
Attach but fail to verify cinder volume: https://bugzilla.redhat.com/show_bug.cgi?id=1427701
marking as resolved in 3.6 with the commit mentioned picked up in 1.6 rebase.
sorry, 3.7 rebase, not 3.6
Can not reproduce the bug on version:
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.