-
Bug
-
Resolution: Unresolved
-
Undefined
-
None
-
None
-
None
-
False
-
-
False
-
?
-
rhos-workloads-compute
-
None
-
-
-
-
Low
https://docs.redhat.com/en/documentation/red_hat_openstack_services_on_openshift/18.0/html/maintaining_the_red_hat_openstack_services_on_openshift_deployment/assembly_shutting-down-and-starting-up-rhoso-nodes#proc_shutting-down-compute-nodes_clean
Command at step 6.4 returns an error
6.4. Shutting down Compute nodes If your Compute nodes are bare-metal nodes that were provisioned when deploying the data plane, annotate the BareMetalHost custom resource (CR) for each Compute node to prevent the Cluster Baremetal Operator (CBO) from rebooting the node: $ oc annotate bmh <compute_node_name> -n openshift-machine-api 'baremetalhost.metal3.io/detached'
The command is missing a value ('=' in this case). It should look like this:
$ oc annotate bmh <compute_node_name> -n openshift-machine-api 'baremetalhost.metal3.io/detached='
Tested using the documented command (/detached) and the suggested one (/detached=):
[m3@lab ~]$ oc annotate bmh rhoso-compute-2 -n openstack 'baremetalhost.metal3.io/detached' error: at least one annotation update is required [m3@lab ~]$ oc annotate bmh rhoso-compute-2 -n openstack 'baremetalhost.metal3.io/detached=' baremetalhost.metal3.io/rhoso-compute-2 annotated
