https://github.com/openshift/origin/pull/21296
Tested on below version: openshift v3.11.50 kubernetes v1.11.0+d4cacc0 # uname -a Linux ocp310.master.vsphere.local 3.10.0-862.3.2.el7.x86_64 #1 SMP Tue May 15 18:22:15 EDT 2018 x86_64 x86_64 x86_64 GNU/Linux # cat /etc/redhat-release Red Hat Enterprise Linux Server release 7.5 (Maipo) # oc get pods NAME READY STATUS RESTARTS AGE rbdpd 1/1 Running 0 1m rbdpd1 1/1 Running 0 1m rbdpd2 1/1 Running 0 52s # mount | grep rbd /dev/rbd0 on /var/lib/origin/openshift.local.volumes/plugins/kubernetes.io/rbd/mounts/rbd-image-kubernetes-dynamic-pvc-fbca0525-f87c-11e8-b698-0050569f4627 type ext4 (rw,relatime,seclabel,stripe=1024,data=ordered,_netdev) /dev/rbd0 on /var/lib/origin/openshift.local.volumes/pods/5424f8de-f87d-11e8-8870-0050569f4627/volumes/kubernetes.io~rbd/pvc-fb999415-f87c-11e8-8870-0050569f4627 type ext4 (rw,relatime,seclabel,stripe=1024,data=ordered,_netdev) /dev/rbd1 on /var/lib/origin/openshift.local.volumes/plugins/kubernetes.io/rbd/mounts/rbd-image-kubernetes-dynamic-pvc-0d4d0e95-f87d-11e8-b698-0050569f4627 type ext4 (rw,relatime,seclabel,stripe=1024,data=ordered,_netdev) /dev/rbd1 on /var/lib/origin/openshift.local.volumes/pods/6055aec8-f87d-11e8-8870-0050569f4627/volumes/kubernetes.io~rbd/pvc-0d46838e-f87d-11e8-8870-0050569f4627 type ext4 (rw,relatime,seclabel,stripe=1024,data=ordered,_netdev) /dev/rbd2 on /var/lib/origin/openshift.local.volumes/plugins/kubernetes.io/rbd/mounts/rbd-image-kubernetes-dynamic-pvc-1839e7a9-f87d-11e8-b698-0050569f4627 type ext4 (rw,relatime,seclabel,stripe=1024,data=ordered,_netdev) /dev/rbd2 on /var/lib/origin/openshift.local.volumes/pods/6c9217d4-f87d-11e8-8870-0050569f4627/volumes/kubernetes.io~rbd/pvc-1835dda6-f87d-11e8-8870-0050569f4627 type ext4 (rw,relatime,seclabel,stripe=1024,data=ordered,_netdev) Then reboot the node, node can be rebooted smoothly. #last reboot | head -1 reboot system boot 3.10.0-862.3.2.e Wed Dec 5 06:10 - 06:15 (00:04)
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