Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1551775

Summary:	Volume not getting unmounted when openshift node process is down and comes back
Product:	OpenShift Container Platform	Reporter:	Hemant Kumar <hekumar>
Component:	Storage	Assignee:	Hemant Kumar <hekumar>
Status:	CLOSED ERRATA	QA Contact:	Jianwei Hou <jhou>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	3.9.0	CC:	aos-bugs, aos-storage-staff, bchilds, eparis, lxia
Target Milestone:	---
Target Release:	3.9.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:	2018-03-28 14:30:19 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 Hemant Kumar 2018-03-05 23:11:56 UTC

Description of problem:


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


How reproducible:
About 50-60% of the time


Steps to Reproduce:
1. Create a pod 
2. Once pod is running, stop openshift node process
3. Delete the pod
4. Pod will be stuck in terminating state
5. Start the openshift node process again
6. Pod gets deleted from api-server but volume never gets unmounted

Actual results:
Volume does not get unmounted even when node process comes back


Expected results:
Volume should be unmounted when node process comes back


Description of problem:

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

How reproducible:

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:

Master Log:

Node Log (of failed PODs):

PV Dump:

PVC Dump:

StorageClass Dump (if StorageClass used by PV/PVC):

Additional info:

Comment 1 Hemant Kumar 2018-03-06 16:10:15 UTC

Opened a PR to revert it : https://github.com/openshift/origin/pull/18849

Comment 3 Jianwei Hou 2018-03-09 10:33:43 UTC

Verified with v3.9.4.

Tested this multiple times on all cloud platforms, the issue is not reproducible now.

Comment 7 errata-xmlrpc 2018-03-28 14:30:19 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/RHBA-2018:0489