-
Notifications
You must be signed in to change notification settings - Fork 253
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature Request "Forced BMH deletion" #1666
Comments
Try to use patch and delete finalizers. BMH will be deleted |
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. |
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. |
I have renamed this issue to represent an actionable feature request. |
yes, we need this feature |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with /lifecycle stale |
/remove-lifecycle stale. |
/remove-lifecycle stale |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with /lifecycle stale |
/remove-lifecycle stale |
What steps did you take and what happened:
[A clear and concise description on how to REPRODUCE the bug.]
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:
/kind bug
The text was updated successfully, but these errors were encountered: