Description of problem:
As part of cnv chaos testing we explored scenarios where we explored how node disruptions like power loss, reboots, suspends (node as vm) affect the workload. We noticed consistent behaviour where workload is rescheduled only when the node is back again. No matter if runStrategy is set to always or the vms are migratable the platform only reacts when the node is back (recovered).

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

How reproducible:
100%

Steps to Reproduce:
1. Schedule workload (vm) to run on specific node
2. Reboot the node
3.

Actual results:
Vms are rescheduled only when the node is back

Expected results:
The cluster workload is rebalanced when node failure, reboot is detected.

Additional info: