Bug 1468719

Summary:	[3.5] Openstack cinder volumes not detached from downed vm when pod is rescheduled to another node.
Product:	OpenShift Container Platform	Reporter:	Ryan Howe <rhowe>
Component:	Node	Assignee:	Robert Rati <rrati>
Status:	CLOSED WONTFIX	QA Contact:	DeShuai Ma <dma>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	3.5.0	CC:	aos-bugs, decarr, eparis, jokerman, mmccomas, rhowe
Target Milestone:	---
Target Release:	3.5.z
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-07-14 15:55:13 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 Ryan Howe 2017-07-07 18:01:21 UTC

Description of problem:
[COPIED FROM UPSTREAM KUBE ISSUE 33288]

If compute instance with attached volume is downed (physical volume in kubernetes terms), kubernetes doesn't try to detach said volume (ever). End result is that k8s is trying to attach a volume in a loop but never succeeds because it is already attached to a downed node.


Version-Release number of selected component (if applicable):
OCP 3.5


What you expected to happen:
I expect node to detach volume before trying to attach it to a new compute instance.

How to reproduce it (as minimally and precisely as possible):
Bring up cluster with two nodes on openstack. Schedule pod with a pvc. Shutdown (from the command line on the operating system) the node with attached volume. Pod gets rescheduled to another node, but volume stays with the downed node.


Additional info:


Upstream issue and fix merged in 1.6, but needing the fix for OpenShift 3.5

https://github.com/kubernetes/kubernetes/issues/33288
https://github.com/kubernetes/kubernetes/pull/39055
https://github.com/kubernetes/kubernetes/commit/fa1d6f38388ebf0def8eebe49fa4e40b4f1b487b