Bug 1626054

Summary:	[3.10] Pod stuck in terminating while a volume mounted with flexvolume driver and XFS filesystem
Product:	OpenShift Container Platform	Reporter:	Seth Jennings <sjenning>
Component:	Storage	Assignee:	Bradley Childs <bchilds>
Status:	CLOSED ERRATA	QA Contact:	Jianwei Hou <jhou>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	3.10.0	CC:	aos-bugs, aos-storage-staff, jokerman, mmccomas, rekhan
Target Milestone:	---
Target Release:	3.10.z
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:	Fixes an issue where a Pod is stuck terminating due to I/O errors on flexvolume mounted XFS filesystem	Story Points:	---
Clone Of:	1625640	Environment:
Last Closed:	2018-11-11 16:39:11 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:
Bug Depends On:	1625640
Bug Blocks:

Description Seth Jennings 2018-09-06 13:17:56 UTC

+++ This bug was initially created as a clone of Bug #1625640 +++

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

--- Additional comment from Seth Jennings on 2018-09-05 10:03:35 EDT ---

Origin PR:
https://github.com/openshift/origin/pull/20866

Comment 3 Jianwei Hou 2018-10-09 10:49:03 UTC

Tested on v3.10.53, could not reproduce the corruption issue, regressively tested flexvolume.

Comment 5 errata-xmlrpc 2018-11-11 16:39:11 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-2018:2709