Can't perform patch request using redfish api

[Gunawan_Jo]

I'm encountering an issue while trying to set the boot target for my HPE server using the Redfish API. I successfully inserted the SPP firmware ISO using the virtual media URL. Now, I want to set the next boot target to that virtual media.

I’m sending a PATCH request to the following endpoint:
https://ip_address/redfish/v1/Systems/1/

Here's the body of the request:

{

    "Boot": {

        "BootSourceOverrideTarget": "Cd",

        "UefiTargetBootSourceOverride": "PciRoot(0x0)/Pci(0x5,0x2)/Pci(0x0,0x4)/USB(0x1,0x0)",

        "BootSourceOverrideEnabled": "Once"

    }

}

However, I keep getting this error response

{

    "error": {

        "code": "iLO.0.10.ExtendedInfo",

        "message": "See @Message.ExtendedInfo for more information.",

        "@Message.ExtendedInfo": [

            {

                "MessageArgs": [

                    "UefiTargetBootSourceOverride"

                ],

                "MessageId": "iLO.2.24.UnableToModifyDuringSystemPOST"

            }

        ]

    }

}

I thought I just needed to wait for the POST to finish, and I've actually waited for a whole day, but the error persists.

Has anyone else faced this issue before? I'm looking forward to any help or suggestions on how to resolve this. Thanks!

[TVVJ]

Hello,

Though not sure about RESTAPIs, the error indicates that the boot source could not be over-ridden during POST. May be the values for the following needs to be reviewed:

  "UefiTargetBootSourceOverride": "PciRoot(0x0)/Pci(0x5,0x2)/Pci(0x0,0x4)/USB(0x1,0x0)"

Regards,

[support_s]

Hello,

Let us know if you were able to resolve the issue.

If you have no further query, and you are satisfied with the answer then kindly mark the topic as Solved so that it is helpful for all community members.

Please click on "Thumbs Up/Kudo" icon to give a "Kudo".

Thank you for being a HPE valuable community member.

[HexaDeci]

I had the same issue you were experiencing except that I did not include "UefiTargetBootSourceOverride" in the payload and still encountered the same error. I waited for the attributes of this endpoint /redfish/v1/systems/1 to be in this state:

"DeviceDiscoveryComplete": 
"AMSDeviceDiscovery": "NoAMS",
"DeviceDiscovery": "vMainDeviceDiscoveryComplete"
}

"PostState": "InPostDiscoveryComplete"

As per API documentation, "Discovery complete is the point at which it has been deemed safe to read and write the BIOS configuration information."
My only workaround was to power off the server, apply the patch, and then turn it back on.

I hope this helps.