Tested on below version:
openshift v3.10.79
kubernetes v1.10.0+b81c8f8

# uname -a
Linux ip-172-18-6-150.ec2.internal 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)

[root@ip-172-18-11-14 ~]# systemctl stop atomic-openshift-node.service 
[root@ip-172-18-11-14 ~]# cd /var/lib/
[root@ip-172-18-11-14 lib]# mv origin openshift
[root@ip-172-18-11-14 lib]# ln -s /var/lib/openshift origin
[root@ip-172-18-11-14 lib]# 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
docker-registry-1-tw2qd    1/1       Running       0          4h
registry-console-1-9vf9k   1/1       Running       0          4h
router-1-jd85h             1/1       Running       0          4h
testpod                    1/1       Terminating   0          1m

[root@ip-172-18-6-150 ~]# oc get pods
NAME                       READY     STATUS    RESTARTS   AGE
docker-registry-1-tw2qd    1/1       Running   0          4h
registry-console-1-9vf9k   1/1       Running   0          4h
router-1-jd85h             1/1       Running   0          4h

Pod can be delete immediately. Thanks Jan for the detain verification steps!!

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:3750