Bug 1696207 - 3.6: Pods stuck in Terminating status when using configmap mounted using subpath volume
Summary: 3.6: Pods stuck in Terminating status when using configmap mounted using subp...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Storage
Version: 3.6.0
Hardware: Unspecified
OS: Unspecified
high
urgent
Target Milestone: ---
: 3.6.z
Assignee: Jan Safranek
QA Contact: Liang Xia
URL:
Whiteboard:
Depends On: 1623053
Blocks: 1640077 1640078 1640079 1696591
TreeView+ depends on / blocked
 
Reported: 2019-04-04 10:48 UTC by ggore
Modified: 2020-05-20 19:54 UTC (History)
9 users (show)

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.
Clone Of: 1623053
Environment:
Last Closed: 2019-06-17 10:28:44 UTC
Target Upstream Version:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2019:0792 0 None None None 2019-06-17 10:28:49 UTC

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
Note You need to log in before you can comment on or make changes to this bug.