Skip to content

Commit 1676c82

Browse files
committed
change
1 parent b3bf7b2 commit 1676c82

File tree

1 file changed

+1
-9
lines changed

1 file changed

+1
-9
lines changed

virt/nodes/virt-triggering-vm-failover-resolving-failed-node.adoc

Lines changed: 1 addition & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -6,15 +6,7 @@ include::_attributes/common-attributes.adoc[]
66

77
toc::[]
88

9-
If a node fails and xref:../../machine_management/deploying-machine-health-checks.adoc#machine-health-checks-about_deploying-machine-health-checks[machine 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.
10-
11-
[NOTE]
12-
====
13-
If you installed your cluster by using xref:../../installing/installing_bare_metal_ipi/ipi-install-overview.adoc#ipi-install-overview[installer-provisioned infrastructure] and you properly configured machine health checks, the following events occur:
14-
15-
* Failed nodes are automatically recycled.
16-
* Virtual machines with xref:../../virt/nodes/virt-node-maintenance.adoc#run-strategies[`runStrategy`] set to `Always` or `RerunOnFailure` are automatically scheduled on healthy nodes.
17-
====
9+
If a node fails and link:https://access.redhat.com/articles/7057929[node health checks] are not deployed on your cluster, virtual machines (VMs) with `runStrategy: Always` configured are not automatically relocated to healthy nodes.
1810

1911
[id="prerequisites_{context}"]
2012
== Prerequisites

0 commit comments

Comments
 (0)