-
Notifications
You must be signed in to change notification settings - Fork 297
Open
Labels
kind/bugCategorizes issue or PR as related to a bug.Categorizes issue or PR as related to a bug.triage/acceptedIndicates an issue is ready to be actively worked on.Indicates an issue is ready to be actively worked on.
Description
What steps did you take and what happened:
When a servicing operation (e.g. firmware update) fails, the BMH ends up in servicing error and there is no easy way to recover from it (other than deleting metal3 pod)
What did you expect to happen:
I'd hope to see a feature in BMO that allows the operator to handle this more cleanly
Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]
Proposed fix incoming
Environment:
- Baremetal Operator version: main branch
- Environment dev-scripts
/kind bug
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
kind/bugCategorizes issue or PR as related to a bug.Categorizes issue or PR as related to a bug.triage/acceptedIndicates an issue is ready to be actively worked on.Indicates an issue is ready to be actively worked on.