Skip to content

Commit ea84b08

Browse files
authored
Merge pull request #81501 from johnwilkins/HCIDOCS-316.2
HCIDOCS-316: Add information about Metal3 database to bare-metal IPI troubleshooting
2 parents 502139d + a775c44 commit ea84b08

File tree

2 files changed

+24
-0
lines changed

2 files changed

+24
-0
lines changed

installing/installing_bare_metal_ipi/ipi-install-post-installation-configuration.adoc

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -25,6 +25,8 @@ include::modules/bmo-about-the-baremetalhost-resource.adoc[leveloffset=+2]
2525
include::modules/bmo-getting-the-baremetalhost-resource.adoc[leveloffset=+2]
2626
// Editing a BareMetalHost resource
2727
include::modules/bmo-editing-a-baremetalhost-resource.adoc[leveloffset=+2]
28+
// Troubleshooting latency.
29+
include::modules/bmo-troubleshooting-latency-when-deleting-a-baremetalhost-resource.adoc[leveloffset=+2]
2830
// Attaching a non-bootable ISO to a bare-metal node
2931
include::modules/bmo-attaching-a-non-bootable-iso-to-a-bare-metal-node.adoc[leveloffset=+2]
3032
// About the HostFirmwareSettings resource
Lines changed: 22 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,22 @@
1+
// Module included in the following assemblies:
2+
// //installing/installing_bare_metal_ipi/installing_bare_metal_ipi/ipi-install-troubleshooting.adoc
3+
4+
:_mod-docs-content-type: PROCEDURE
5+
[id="ipi-install-troubleshooothing-latency-when-deleting-a-baremetalhost-resource_{context}"]
6+
7+
= Troubleshooting latency when deleting a BareMetalHost resource
8+
9+
When the Bare Metal Operator (BMO) deletes a `BareMetalHost` resource, Ironic deprovisions the bare-metal host with a process called cleaning. When cleaning fails, Ironic retries the cleaning process three times, which is the source of the latency. The cleaning process might not succeed, causing the provisioning status of the bare-metal host to remain in the *deleting* state indefinitely. When this occurs, use the following procedure to disable the cleaning process.
10+
11+
[WARNING]
12+
====
13+
Do not remove finalizers from the `BareMetalHost` resource.
14+
====
15+
16+
.Procedure
17+
18+
. If the cleaning process fails and restarts, wait for it to finish. This might take about 5 minutes.
19+
20+
. If the provisioning status remains in the *deleting* state, disable the cleaning process by modifying the `BareMetalHost` resource and setting the `automatedCleaningMode` field to `disabled`.
21+
22+
See "Editing a BareMetalHost resource" for additional details.

0 commit comments

Comments
 (0)