1
0
mirror of https://github.com/openshift/openshift-docs.git synced 2026-02-05 12:46:18 +01:00
Files
openshift-docs/virt/nodes/virt-triggering-vm-failover-resolving-failed-node.adoc
Sabrina Jess fc57149491 change
2024-09-06 14:44:03 +00:00

26 lines
1.3 KiB
Plaintext

:_mod-docs-content-type: ASSEMBLY
[id="virt-triggering-vm-failover-resolving-failed-node"]
= Deleting a failed node to trigger virtual machine failover
include::_attributes/common-attributes.adoc[]
:context: virt-triggering-vm-failover-resolving-failed-node
toc::[]
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.
[id="prerequisites_{context}"]
== Prerequisites
* A node where a virtual machine was running has the `NotReady` xref:../../nodes/nodes/nodes-nodes-viewing.adoc#nodes-nodes-viewing-listing_nodes-nodes-viewing[condition].
* The virtual machine that was running on the failed node has `runStrategy` set to `Always`.
* You have installed the OpenShift CLI (`oc`).
include::modules/nodes-nodes-working-deleting-bare-metal.adoc[leveloffset=+1]
[id="verifying-vm-failover_{context}"]
== Verifying virtual machine failover
After all resources are terminated on the unhealthy node, a new virtual machine instance (VMI) is automatically created on a healthy node for each relocated VM. To confirm that the VMI was created, view all VMIs by using the `oc` CLI.
include::modules/virt-listing-vmis-cli.adoc[leveloffset=+2]