Skip to content

Commit c5b30a7

Browse files
authored
Merge pull request #56878 from rohennes/TELCODOCS-654-unhealthy-etcd
TELCODOCS-654: updating procedure to make it work for IPI baremetal installs
2 parents b83722c + 6d9f107 commit c5b30a7

File tree

2 files changed

+33
-36
lines changed

2 files changed

+33
-36
lines changed

modules/restore-replace-stopped-baremetal-etcd-member.adoc

Lines changed: 24 additions & 32 deletions
Original file line numberDiff line numberDiff line change
@@ -316,41 +316,57 @@ NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE MESSAGE
316316
baremetal 4.12.0 True False False 3d15h
317317
----
318318

319-
. Delete the machine of the unhealthy member using this command:
319+
. Remove the old `BareMetalHost` object by running the following command:
320+
+
321+
[source,terminal]
322+
----
323+
$ oc delete bmh openshift-control-plane-2 -n openshift-machine-api
324+
----
325+
+
326+
.Example output
327+
[source,terminal]
328+
----
329+
baremetalhost.metal3.io "openshift-control-plane-2" deleted
330+
----
331+
332+
. Delete the machine of the unhealthy member by running the following command:
320333
+
321334
[source,terminal]
322335
----
323336
$ oc delete machine -n openshift-machine-api examplecluster-control-plane-2
324337
----
325338
+
339+
After you remove the `BareMetalHost` and `Machine` objects, then the `Machine` controller automatically deletes the `Node` object.
340+
+
326341
If deletion of the machine is delayed for any reason or the command is obstructed and delayed, you can force deletion by removing the machine object finalizer field.
327342
+
328343
[IMPORTANT]
329344
====
330345
Do not interrupt machine deletion by pressing `Ctrl+c`. You must allow the command to proceed to completion. Open a new terminal window to edit and delete the finalizer fields.
331346
====
332347
+
348+
.. Edit the machine configuration by running the following command:
349+
+
333350
[source,terminal]
334351
----
335352
$ oc edit machine -n openshift-machine-api examplecluster-control-plane-2
336353
----
337354
+
338-
.. Find and delete the fields:
355+
.. Delete the following fields in the `Machine` custom resource, and then save the updated file:
339356
+
340-
[source,terminal]
357+
[source,yaml]
341358
----
342359
finalizers:
343360
- machine.machine.openshift.io
344361
----
345362
+
346-
Save your changes:
347-
+
363+
.Example output
348364
[source,terminal]
349365
----
350366
machine.machine.openshift.io/examplecluster-control-plane-2 edited
351367
----
352-
+
353-
.. Verify the machine was deleted by running the following command:
368+
369+
. Verify that the machine was deleted by running the following command:
354370
+
355371
[source,terminal]
356372
----
@@ -366,32 +382,8 @@ examplecluster-control-plane-1 Running 3h11m opens
366382
examplecluster-compute-0 Running 165m openshift-compute-0 baremetalhost:///openshift-machine-api/openshift-compute-0/3d685b81-7410-4bb3-80ec-13a31858241f provisioned
367383
examplecluster-compute-1 Running 165m openshift-compute-1 baremetalhost:///openshift-machine-api/openshift-compute-1/0fdae6eb-2066-4241-91dc-e7ea72ab13b9 provisioned
368384
----
369-
370-
. Remove the old `BareMetalHost` object with this command:
371-
+
372-
[source,terminal]
373-
----
374-
$ oc delete bmh openshift-control-plane-2 -n openshift-machine-api
375-
----
376-
+
377-
.Example output
378-
[source,terminal]
379-
----
380-
baremetalhost.metal3.io "openshift-control-plane-2" deleted
381-
----
382-
+
383-
After you remove the `BareMetalHost` and `Machine` objects, then the `Machine` controller automatically deletes the `Node` object.
384-
+
385-
If, after deletion of the `BareMetalHost` object, the machine node requires excessive time for deletion, the machine node can be deleted using:
386-
+
387-
[source,terminal]
388-
----
389-
$ oc delete node openshift-control-plane-2
390-
391-
node "openshift-control-plane-2" deleted
392-
----
393385
+
394-
Verify the node has been deleted:
386+
. Verify that the node has been deleted by running the following command:
395387
+
396388
[source,terminal]
397389
----

modules/restore-replace-stopped-etcd-member.adoc

Lines changed: 9 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -266,13 +266,19 @@ metadata:
266266
providerID: aws:///us-east-1a/i-0fdb85790d76d0c3f
267267
----
268268

269-
.. Delete the machine of the unhealthy member:
269+
.. Delete the `BareMetalHost` object by running the following command, replacing `<host_name>` with the name of the bare-metal host for the unhealthy node:
270270
+
271271
[source,terminal]
272272
----
273-
$ oc delete machine -n openshift-machine-api clustername-8qw5l-master-0 <1>
273+
$ oc delete bmh -n openshift-machine-api <host_name>
274+
----
275+
276+
.. Delete the machine of the unhealthy member by running the following command, replacing `<machine_name>` with the name of the control plane machine for the unhealthy node, for example `clustername-8qw5l-master-0`:
277+
+
278+
[source,terminal]
279+
----
280+
$ oc delete machine -n openshift-machine-api <machine_name>
274281
----
275-
<1> Specify the name of the control plane machine for the unhealthy node.
276282

277283
.. Verify that the machine was deleted:
278284
+
@@ -299,7 +305,6 @@ clustername-8qw5l-worker-us-east-1c-pkg26 Running m4.large us-east-1 us
299305
$ oc apply -f new-master-machine.yaml
300306
----
301307

302-
303308
.. Verify that the new machine has been created:
304309
+
305310
[source,terminal]

0 commit comments

Comments
 (0)