Skip to content

bug: After RMS based Firmware Update suceeds, state machine transitions to HostReprovisioning/CheckingFirmwareRepeatV2 #2016

@anunna0

Description

@anunna0

Version

0.10-rc1

Describe the bug.

After RMS completed the SOT JSON firmware update, BMM was still sending the host into CheckingFirmwareRepeatV2.

That state uses BMM’s old local firmware config, not the SOT JSON. So BMM could decide HGXBmc still needed an update and start a second legacy Redfish firmware update. That second update failed and put the host in FailedFirmwareUpgrade.

Fix: when rack/RMS firmware completes, go straight to the completed host state (Ready) instead of CheckingFirmwareRepeatV2.

Minimum reproducible example

Initiate a compute tray update via component manager API with RMS backend and state machine enabled. RMS firmware update will succeed, but mh show will show a failed state.

Relevant log output

Other/Misc.

No response

Code of Conduct

  • I agree to follow NCX Infra Controller's Code of Conduct
  • I have searched the open bugs and have found no duplicates for this bug report

Metadata

Metadata

Assignees

Labels

bugA defect in existing software (deprecated - use issue type, but it's needed for reporting now)

Type

No fields configured for Bug.

Projects

Status
In Progress

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions