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