Bug 1625640 - Pod stuck in terminating while a volume mounted with flexvolume driver and XFS filesystem
Summary: Pod stuck in terminating while a volume mounted with flexvolume driver and XF...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Node
Version: 3.10.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: 3.11.0
Assignee: Seth Jennings
QA Contact: Jianwei Hou
URL:
Whiteboard:
Depends On:
Blocks: 1626054
TreeView+ depends on / blocked
 
Reported: 2018-09-05 12:25 UTC by rehan
Modified: 2018-10-11 07:26 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
undefined
Clone Of:
: 1626054 (view as bug list)
Environment:
Last Closed: 2018-10-11 07:25:56 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2018:2652 0 None None None 2018-10-11 07:26:36 UTC

Description rehan 2018-09-05 12:25:50 UTC 
Description of problem:

POD called to be deleted is stuck infinitely on 'Terminating' while it has a volume mounted with flexvolume driver and XFS filesystem was shutdown due to IO error on the drive.


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

openshift 3.10
How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:
pods failed to get removed. 
The pod stuck in terminating state. 
Expected results:

The pod should get deleted successfully 

Additional info: 

https://github.com/kubernetes/kubernetes/issues/67072
Comment 1 Seth Jennings 2018-09-05 14:03:35 UTC 
Origin PR:
https://github.com/openshift/origin/pull/20866
Comment 3 Jianwei Hou 2018-09-17 11:27:27 UTC 
Could not reproduce the corruption issue, regressively tested flexvolume.
Comment 5 errata-xmlrpc 2018-10-11 07:25:56 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:2652
Note You need to log in before you can comment on or make changes to this bug.