Skip to content

BMO is lacking an easy way to recover from servicing failure #3001

@jacob-anders

Description

@jacob-anders

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    kind/bugCategorizes issue or PR as related to a bug.triage/acceptedIndicates an issue is ready to be actively worked on.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions