Feature Request "Forced BMH deletion"

[matthewei]

What steps did you take and what happened:
[A clear and concise description on how to REPRODUCE the bug.]

matthew@ubuntu:~/github/metal3_dev/baremetal-operator|main⚡ ⇒  kubectl get bmh -A              
NAMESPACE   NAME                   STATE                        CONSUMER   ONLINE   ERROR   AGE
default     cmss-baremetalhost-1   powering off before delete              true             2m58s
matthew@ubuntu:~/github/metal3_dev/baremetal-operator|main⚡ ⇒  

What did you expect to happen:

Delete the BMH directly!

Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]

Environment:

• Baremetal Operator version:
• Environment (metal3-dev-env or other):

/kind bug

[agewagra]

Try to use patch and delete finalizers. BMH will be deleted

[dtantsur]

Try to use patch and delete finalizers.

Please, PLEASE, never recommend anyone to delete finalizers, especially if they don't know 100% what they are doing. In this case, you can and probably will leave a dangling Node in Ironic.

[dtantsur]

On the topic of the request: I think we miss a way to force-delete BareMetalHosts. The reason BMO works the way it works is to try leave the host in a safe state. E.g. a powered on worker can try to rejoin the cluster, messing up CAPI.

[Rozzii]

I have renamed this issue to represent an actionable feature request.
I agree with @dtantsur that we don't have forced BMH deletion and that could come handy for many users.
/triage accepted
/kind feature

[matthewei]

I have renamed this issue to represent an actionable feature request. I agree with @dtantsur that we don't have forced BMH deletion and that could come handy for many users. /triage accepted /kind feature

yes, we need this feature

[metal3-io-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues will close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[Rozzii]

/remove-lifecycle stale.

[Rozzii]

/remove-lifecycle stale

[metal3-io-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues will close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[mquhuy]

/remove-lifecycle stale

[hardys]

I wonder if one way to achieve this is to fix #1729 so that it's possible to apply the detached annotation (which removes the node from Ironic), then delete the BMH (which should result in no finalizer related actions)?

It should already be possible to try this other than the race mentioned in #1729 so would be good to confirm if this is logically equivalent to the desired behavior