Bug 1640078 - 3.11: Pods stuck in Terminating status when using configmap mounted using subpath volume
Summary: 3.11: Pods stuck in Terminating status when using configmap mounted using sub...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Storage
Version: 3.11.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 3.11.0
Assignee: Bradley Childs
QA Contact: Wenqi He
URL:
Whiteboard:
Depends On: 1623053 1640079 1696207 1696591
Blocks: 1640077
TreeView+ depends on / blocked
 
Reported: 2018-10-17 10:47 UTC by Jan Safranek
Modified: 2020-05-20 19:54 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1623053
Environment:
Last Closed: 2018-12-12 14:15:51 UTC
Target Upstream Version:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2018:3743 0 None None None 2018-12-12 14:16:01 UTC

Comment 5 Wenqi He 2018-11-29 10:38:57 UTC 
Tested on below version:
openshift v3.11.43
kubernetes v1.11.0+d4cacc0

# uname -a
Linux preserver-qe-piqin-1-mrre-1 3.10.0-957.el7.x86_64 #1 SMP Thu Oct 4 20:48:51 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
# cat /etc/redhat-release 
Red Hat Enterprise Linux Server release 7.6 (Maipo)

# systemctl stop atomic-openshift-node.service 
# cd /var/lib/
# mv origin openshift
# ln -s /var/lib/openshift origin
# systemctl start atomic-openshift-node.service

After create a symlink and schedule the subpath pod to this node, and then
delete it

[root@ip-172-18-6-150 ~]# oc get pods
NAME                       READY     STATUS        RESTARTS   AGE
testpod                    1/1       Terminating   0          1m

[root@ip-172-18-6-150 ~]# oc get pods

Pod can be delete immediately.
Comment 7 errata-xmlrpc 2018-12-12 14:15:51 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:3743
Note You need to log in before you can comment on or make changes to this bug.