Redfish - Future State (SD) - AsRock Rack

Bug #2073518 reported by Alexander Birkner
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Ironic
New
Undecided
Unassigned

Bug Description

Currently we are using Redfish as driver for all our systems, that is working fine when using DELL, HPE or SuperMicro machines. Unfortunately we received test machines with an AsRock Rack mainboard which supports Redfish but sadly not working with Ironic.

Once the management interface tries to set the boot device to PXE (for next boot) it fails with an error:

{"error":{"@Message.ExtendedInfo":[{"@odata.type":"#Message.v1_0_8.Message","Message":"Support of this Operation for Boot Properties is moved to FutureState URI(/redfish/v1/Systems/Self/SD)","MessageArgs":["Boot","/redfish/v1/Systems/Self/SD"],"MessageId":"Ami.1.0.OperationSupportedInFutureStateURI","RelatedProperties":["#/Boot"],"Resolution":"Repeat the operation on FutureState(SD) URI for applying these changes","Severity":"Critical"}],"code":"Ami.1.0.OperationSupportedInFutureStateURI","message":"Support of this Operation for Boot Properties is moved to FutureState URI(/redfish/v1/Systems/Self/SD)"}}

I am really wondering if the future state thing is even existing in the RFC of Redfish but that case needs to be handled properly to support AsRock Rack. But at least I found also documentation from Lenovo, so AsRock is not the only one.

See:
https://pubs.lenovo.com/tsm/patch_systems_instance_sd

Revision history for this message
Alexander Birkner (tyrola) wrote :

I have tested using the SD endpoint instead using a AsRock Rack machine is working properly. The machine rebooted to PXE.

The example code is attached.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.