Description of problem:
After a power outage when trying to start a VM, virt-launcher was stuck in a terminating status.

Version-Release number of selected component (if applicable):
version: 4.12.5

How reproducible:
1 time as we can see

Steps to Reproduce:
1.
2.
3.

Actual results:

• lost power
• nodes went into weird state
• looked like unhealthy node, node2
• restarted network service on node 2

a few minutes later, the VM_1 is showing 'stopping'

• both VM_2 and VM_1 were running on node3

• Did a force delete of VM_1 after waiting the full hour to be safe.

• VM_1 terminating while trying to start on node 'node2', while it was previously running on 'node3' along with VM_2.
  ~~~
  $ oc get pods
  NAME READY STATUS RESTARTS AGE
  virt-launcher-VM_1-rdzbm 0/1 Terminating 0 109m
  virt-launcher-VM_2-vqq7s 1/1 Running 0 3h
  virt-launcher-VM_2-xh66s 0/1 Error 0 76m <----- this was a migration attempt of the vm OFF node 3 in order to reboot and the migration failed.
  ~~~

Expected results:
After an outage to be able to start the guest

Additional info:

• Storage is portworx