Bug 1888072
Summary: | Setting Supermicro node to PXE boot via Redfish doesn't take affect | ||||||
---|---|---|---|---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Bob Fournier <bfournie> | ||||
Component: | Bare Metal Hardware Provisioning | Assignee: | Bob Fournier <bfournie> | ||||
Bare Metal Hardware Provisioning sub component: | ironic | QA Contact: | Raviv Bar-Tal <rbartal> | ||||
Status: | CLOSED ERRATA | Docs Contact: | |||||
Severity: | high | ||||||
Priority: | high | CC: | dblack, rbartal, smalleni, tsedovic | ||||
Version: | 4.6 | Keywords: | OtherQA, TestBlocker, Triaged | ||||
Target Milestone: | --- | ||||||
Target Release: | 4.7.0 | ||||||
Hardware: | Unspecified | ||||||
OS: | Unspecified | ||||||
Whiteboard: | |||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||
Doc Text: |
Cause: During deployment, Supermicro nodes require the setting of the boot mode along with the boot device when using Redfish, otherwise it reverts the boot mode to "Legacy".
Consequence: Cannot deploy Supermicro nodes using Redfish.
Fix: Set the boot mode in Supermicro if it got changed after setting the boot device.
Result: Can properly deploy Supermicro nodes.
|
Story Points: | --- | ||||
Clone Of: | |||||||
: | 1888375 1892302 (view as bug list) | Environment: | |||||
Last Closed: | 2021-02-24 15:25:41 UTC | Type: | Bug | ||||
Regression: | --- | Mount Type: | --- | ||||
Documentation: | --- | CRM: | |||||
Verified Versions: | Category: | --- | |||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
Cloudforms Team: | --- | Target Upstream Version: | |||||
Embargoed: | |||||||
Bug Depends On: | |||||||
Bug Blocks: | 1888375, 1892302 | ||||||
Attachments: |
|
Description
Bob Fournier
2020-10-14 00:13:10 UTC
Created attachment 1721450 [details]
Ironic-conductor log file setting node to PXE boot which doesn't take affect
Looks like the issue is that we need to set the mode to UEFI prior to PXE booting as it ends up reverting back to Legacy - 'BootSourceOverrideMode': 'Legacy',. Working on a patch. The Supermicro seems to require the setting of the boot mode along with the boot device when using Redfish, otherwise it reverts the boot mode to "Legacy". Can illustrate this with a simple case: Start with these 2 settings for $ curl -k --user XXXX https://10.1.41.239/redfish/v1/Systems/1/ | jq . "Boot": { "BootSourceOverrideEnabled": "Continuous", "BootSourceOverrideMode": "UEFI", "BootSourceOverrideTarget": "Pxe", Then change only BootSourceOverrideEnabled and BootSourceOverrideTarget $ curl -k --user XXXX -X PATCH -d '{"Boot": {"BootSourceOverrideTarget": "Pxe", "BootSourceOverrideEnabled": "Once"}}' https://10.1.41.239/redfish/v1/Systems/1/ The mode has flipped to Legacy $ curl -k --user XXXX -X PATCH -d '{"Boot": {"BootSourceOverrideTarget": "Pxe", "BootSourceOverrideEnabled": "Once"}}' https://10.1.41.239/redfish/v1/Systems/1/ "Boot": { "BootSourceOverrideEnabled": "Once", "BootSourceOverrideMode": "Legacy", "BootSourceOverrideTarget": "Pxe", We've confirmed with Supermicro that the boot mode ("BootSourceOverrideMode") must be set in the Redfish request when setting the device ( "BootSourceOverrideTarget" and "BootSourceOverrideEnabled"). This is different than other vendors like Dell and HPE which require that the mode NOT be set in the same request - see https://review.opendev.org/#/c/710846/. I have a patch upstream that will fix the issue for Supermicro and not break other vendors - https://review.opendev.org/#/c/758856/. We've verified that nodes boot properly to PXE with this patch. It's still pending upstream reviews. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Moderate: OpenShift Container Platform 4.7.0 security, bug fix, and enhancement update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2020:5633 |