Bug 1625640 – Pod stuck in terminating while a volume mounted with flexvolume driver and XFS filesystem

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

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...

Status:	CLOSED ERRATA

Aliases:	None

Product:	OpenShift Container Platform
Classification:	Red Hat
Component:	Pod (Show other bugs)
Sub Component:
Version:	3.10.0
Hardware:	Unspecified Unspecified

Priority	unspecified Severity unspecified
Target Milestone:	---
Target Release:	3.11.0
Assigned To:	Seth Jennings
QA Contact:	Jianwei Hou
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:	1626054
	Show dependency tree / graph

Reported:	2018-09-05 08:25 EDT by rehan
Modified:	2018-10-11 03:26 EDT (History)
CC List:	3 users (show)

See Also:
Fixed In Version:
Doc Type:	No Doc Update
Doc Text:	undefined
Story Points:	---
Clone Of:
Clones:	1626054 (view as bug list)
Environment:
Last Closed:	2018-10-11 03:25:56 EDT
Type:	Bug
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
Red Hat Product Errata	RHBA-2018:2652	None	None	None	2018-10-11 03:26 EDT

Groups: None (edit)

Description rehan 2018-09-05 08:25:50 EDT

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 10:03:35 EDT

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

Comment 3 Jianwei Hou 2018-09-17 07:27:27 EDT

Could not reproduce the corruption issue, regressively tested flexvolume.

Comment 5 errata-xmlrpc 2018-10-11 03:25:56 EDT

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.