Bug 1551775 - Volume not getting unmounted when openshift node process is down and comes back
Summary: Volume not getting unmounted when openshift node process is down and comes back
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Storage
Version: 3.9.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: 3.9.0
Assignee: Hemant Kumar
QA Contact: Jianwei Hou
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-03-05 23:11 UTC by Hemant Kumar
Modified: 2018-03-28 14:30 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-03-28 14:30:19 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2018:0489 0 None None None 2018-03-28 14:30:51 UTC

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


Note You need to log in before you can comment on or make changes to this bug.