Skip to content

Fix: VeraRubin host BMC displays boot order in a different format#168

Open
hakhondzadeh wants to merge 3 commits into
NVIDIA:mainfrom
hakhondzadeh:VR_boot_order
Open

Fix: VeraRubin host BMC displays boot order in a different format#168
hakhondzadeh wants to merge 3 commits into
NVIDIA:mainfrom
hakhondzadeh:VR_boot_order

Conversation

@hakhondzadeh

Copy link
Copy Markdown

Redfish path redfish/v1/Systems/System_0 for a Vera Rubin host bmc, show boot orders in this format:
"BootOrder": [ "Boot0019: Ubuntu", "Boot0008: UEFI HTTPv4 (MAC:AC3AE2634C82)",
While previously, we saw them in this format:

"BootOrder": [
"Boot0002",
"Boot0001",
"Boot0000"
],
This PR fixes this issue so that boot order is properly added to exploration report.

/// is classified as Vera Rubin (`Vendor=NVIDIA`, `Product=VR NVL72`).
#[cfg(feature = "boot-options")]
#[must_use]
pub fn boot_option_matches_boot_order_entry(

@poroh poroh Jul 25, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This solution is not ideal because it requires user to know that this is the only way to match boot option to boot order entry. I would suggest to add patch support for ComputerSystem item and remove ": " before deserialization to ComputerSystemSchema.

All user logic will remain the same as today.

To do this you need to introduce additional patch function similar to:

if bmc.quirks.bug_empty_uuid_field() {

You can find couple similar functions nearby.

@poroh poroh left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

See my comment.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants