-
Bug
-
Resolution: Done
-
Normal
-
None
-
CNV v4.16.0
-
None
Description of problem:
We want to guide our users to use NHC, not MHC .
Version-Release number of selected component (if applicable):
4.16
Steps to Reproduce:
1. Read https://docs.openshift.com/container-platform/4.15/virt/nodes/virt-triggering-vm-failover-resolving-failed-node.html#virt-triggering-vm-failover-resolving-failed-node 2. 3.
Actual results:
If a node fails and machine <https://docs.openshift.com/container-platform/4.15/machine_management/deploying-machine-health-checks.html#machine-health-checks-about_deploying-machine-health-checks> health checks are not deployed on your cluster, virtual machines (VMs) with runStrategy: Always configured are not automatically relocated to healthy nodes. To trigger VM failover, you must manually delete the Node object.
Expected results:
If a node fails and node <https://access.redhat.com/articles/7057929> health checks are not deployed on your cluster, virtual machines (VMs) with runStrategy: Always configured are not automatically relocated to healthy nodes. To trigger VM failover, you must manually delete the Node object.
Additional info:
- relates to
-
CNV-33030 [2239560] MHC: services within the node did not restart.
- New
- links to