-
Bug
-
Resolution: Not a Bug
-
Normal
-
None
-
Quality / Stability / Reliability
-
False
-
-
False
-
DFG:OSPK8S
-
CLOSED
-
Moderate
-
No
Description of problem:
hard reset (echo b>/proc/sysrq-trigger) of a openshift node holding the vmi causes the vmi to become suspended and unreachable:
How to reproduce :
#sshing to a ocp node hosting the vmi:
[ocp@titan88 ~]$ ssh core@192.168.111.10 (ocp node)
echo 'b'>/proc/sysrq-trigger
vmi controller-0 hangs :
[ocp@titan88 ~]$ virtctl console controller-0
Successfully connected to controller-0 console. The escape sequence is ^]
#no response...
[ocp@titan88 ~]$ oc get pods -o wide
virt-launcher-controller-0-pr4nz 1/1 Running 0 47m 10.129.0.92 ostest-master-1 <none> <none>
[ocp@titan88 ~]$ oc exec -it virt-launcher-controller-0-pr4nz bash
kubectl exec [POD] [COMMAND] is DEPRECATED and will be removed in a future version. Use kubectl exec [POD] – [COMMAND] instead.
[root@controller-0 /]# virsh list
Id Name State
---------------------------------------
1 openstack_controller-0 paused
- external trackers