Add how to delete a BMH in Ironic in the troubleshooting guide

[e-minguez]

Related to suse-edge/charts#121

Basically when a host is being force deleted by removing the finalizers, the ironic database needs to be fixed.

IIRC if using SQLite (the default starting in 3.3), it is enough to restart the ironic pod but if using MariaDB a series of steps need to be done as per suse-edge/charts#121

[hardys]

In general we should use the detached annotation - removing the finalizer (on any resource) should always be a last resort as even with manual cleanup it's quite easy to leave things in an inconsistent state

[ranjinimn]

@e-minguez @hardys can you please let me know the changes I need to make in this request?

[ranjinimn]

@e-minguez I see that a warning is included in the documentation to not remove the finalizer manually.
Do you want me to mention in the same section that if the user is using SQLite, restart the Ironic pod and if the user is using Maria DB, do you want me to provide the configuration file as mentioned in the suse-edge/charts#121?
for MariaDB, are those the steps that user needs to follow to fix it?

[e-minguez]

@e-minguez I see that a warning is included in the documentation to not remove the finalizer manually. Do you want me to mention in the same section that if the user is using SQLite, restart the Ironic pod and if the user is using Maria DB, do you want me to provide the configuration file as mentioned in the suse-edge/charts#121? for MariaDB, are those the steps that user needs to follow to fix it?

I'd say basically to document the "detached" annotation as Steve said. Then, if nothing works, if the user is using SQLite, restart the Ironic pod, otherwise, follow the steps mentioned on mentioned in the suse-edge/charts#121 issue.