Bug 1696207

Summary:	3.6: Pods stuck in Terminating status when using configmap mounted using subpath volume
Product:	OpenShift Container Platform	Reporter:	ggore
Component:	Storage	Assignee:	Jan Safranek <jsafrane>
Status:	CLOSED ERRATA	QA Contact:	Liang Xia <lxia>
Severity:	urgent	Docs Contact:
Priority:	high
Version:	3.6.0	CC:	aos-bugs, aos-storage-staff, bchilds, cstark, jkaur, jmalde, jsafrane, lxia, rekhan
Target Milestone:	---	Keywords:	Rebase
Target Release:	3.6.z
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:	Cause: atomic-openshift-node service did not check for symlinks in /var/lib/origin. Consequence: ConfigMaps, Secrets, DownwardAPI and Projected volumes with subpath were not cleaned up properly and pods were stuck in Terminating state forever. Fix: atomic-openshift-node service properly resolves symlinks in /var/lib/origin path. Result: Pods are cleaned properly.	Story Points:	---
Clone Of:	1623053	Environment:
Last Closed:	2019-06-17 10:28:44 UTC	Type:	---
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:	1623053
Bug Blocks:	1640077, 1640078, 1640079, 1696591

Comment 3 Wenqi He 2019-04-25 06:38:30 UTC

Should we drop this bug from the errata? This bug still repros and what I checked with the PR in comment#1 is not merged.

Comment 7 Wenqi He 2019-05-07 06:05:33 UTC

Tested on below version:
openshift v3.6.173.0.164
kubernetes v1.6.1+5115d708d7

Follow the steps Jan provided, the pod using configmap mounted by subpath has been deleted immediately.

Comment 8 Wenqi He 2019-05-07 06:06:52 UTC

Tested on below version:
openshift v3.6.173.0.164
kubernetes v1.6.1+5115d708d7

Follow the steps Jan provided, the pod using configmap mounted by subpath has been deleted immediately.

Comment 11 errata-xmlrpc 2019-06-17 10:28:44 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-2019:0792