[BUG]: Certain SMC SKUs (ARS-121L-DNR) are intermittently reporting an incorrect boot order via Redfish #505
Description
Version
v0.2.0-rc15
Which installation method(s) does this occur on?
No response
Describe the bug.
For some Supermicro x86_64 systems (ARS-121L-DNR), we have observed that the BIOS and BMC disagree on the boot order. efibootmgr was showing disk,net,shell. Redfish was showing net,disk,shell. Reboot after reboot with lockdown mode on, nothing changed. I disabled lockdown and rebooted, and redfish updated to match efibootmgr.
So our code to change the boot order doesn't trigger, as redfish is telling us that it's already correct. This seems like a bug for Supermicro, if lockdown doesn't stop the tenant OS from changing it, then redfish should reflect the change, it shouldn't block it from showing reality. However, maybe we could work around it by disabling lockdown as one of the first steps in termination, and leaving it off until we get a successful boot of scout?
My test system was running..
Supermicro firmware 01.03.50
Redfish 1.21.0
BIOS 2.5
CPLD F2.41.36
Minimum reproducible example
Relevant log output
Other/Misc.
No response
Code of Conduct
- I agree to follow NVIDIA Bare Metal Manager's Code of Conduct
- I have searched the open bugs and have found no duplicates for this bug report