Skip to content

Commit 109f2a1

Browse files
authored
Merge pull request #34841 from mburke5678/BZ-1877387
BZ:1877387: Incorrect command for deleting a baremetal node in the docs
2 parents 96dc080 + ceb51dc commit 109f2a1

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

virt/install/preparing-cluster-for-virt.adoc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -24,7 +24,7 @@ xref:../../installing/installing_bare_metal/installing-bare-metal.adoc#installin
2424
In {VirtProductName} clusters installed using installer-provisioned infrastructure and with MachineHealthCheck properly configured, if a node fails the MachineHealthCheck and becomes unavailable to the cluster, it is recycled. What happens next with VMs that ran on the failed node depends on a series of conditions. See xref:../../virt/virtual_machines/virt-create-vms.adoc#virt-about-runstrategies-vms_virt-create-vms[About RunStrategies for virtual machines] for more detailed information about the potential outcomes and how RunStrategies affect those outcomes.
2525
====
2626

27-
** If you are not using installer-provisioned infrastructure, use either a monitoring system or a qualified human to monitor node availability. When a node is lost, shut it down and run `oc adm delete node <lost_node>`.
27+
** If you are not using installer-provisioned infrastructure, use either a monitoring system or a qualified human to monitor node availability. When a node is lost, shut it down and run `oc delete node <lost_node>`.
2828
+
2929
[NOTE]
3030
====

0 commit comments

Comments
 (0)