Bug 1473770

Summary: Cinder volume not attaching to the Pod
Product: OpenShift Container Platform Reporter: jliberma <jliberma>
Component: StorageAssignee: Bradley Childs <bchilds>
Status: CLOSED ERRATA QA Contact: Qin Ping <piqin>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 3.5.0CC: aos-bugs, aos-storage-staff, eparis, jeffrey.r.morgan.jr
Target Milestone: ---   
Target Release: 3.7.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-11-28 22:05:05 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description jliberma@redhat.com 2017-07-21 15:06:44 UTC
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

Comment 1 Eric Paris 2017-07-22 17:07:19 UTC
marking as resolved in 3.6 with the commit mentioned picked up in 1.6 rebase.

Comment 2 Eric Paris 2017-07-22 17:23:46 UTC
sorry, 3.7 rebase, not 3.6

Comment 4 Qin Ping 2017-10-09 07:58:04 UTC
Can not reproduce the bug on version:
openshift v3.7.0-0.144.2
kubernetes v1.7.6+a08f5eeb62

Comment 7 errata-xmlrpc 2017-11-28 22:05:05 UTC
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