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) How reproducible: Every time. 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. Actual results: After manually detaching Cinder volume from an Openstack instance, it get's attached again and the error repeats. Expected results: Cinder volume gets mounted to a pod and pod goes to a 'Running' state Additional info: This is the upstream bug report and workaround: https://github.com/kubernetes/kubernetes/issues/34698#issuecomment-282129378 This is the upstream fix: https://github.com/kubernetes/kubernetes/pull/41498 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: openshift v3.7.0-0.144.2 kubernetes v1.7.6+a08f5eeb62
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