Greetings,

Without knowing the hardware being used, along with the firmware on the BMC (meaning version), there really is not much we can do to assist. Ultimately setting a machine to UEFI is a standard procedure defined in the Redfish protocol, and if the remote BMC is not liking that request, then some research needs to be performed.

There *is* a distinct possibility that it could be something like ETAG handling with the request that it doesn't like. I'd recommend using a more recent, supported, version of Ironic to see.

-Julia

On Wed, Jul 31, 2024 at 11:26 PM Ali Hussain <alihussain448@gmail.com> wrote:
Hello Everyone,

We are having issue deploying Ironic baremental image to compute using Ironic(Yoga). The Baremetal machine is enrolled using Redfish driver. It goes to Available state as well. Once we attempt to deploy it the following exception is thrown.

Error: Detected change in error condition on node “BMNode1”. 

Deploy step deploy.deploy failed: Redfish exception occurred. 

Error: Setting boot mode to uefi failed for node <UUID>. 

Error: HTTP PATCH http://IP/redfish/v1/Systems/1 returned code 400. Base.v1_10_3.GeneralError: The service detected a malformed request body that it was unable to interpret. 

Extended information: 

[{'MessageId': 'Base.1.10.UnrecognizedRequestBody', 'Severity': 'Warning', 'Resolution': 'Correct the request body and resubmit the request if it failed.', 'Message': 'The service detected a malformed request body that it was unable to interpret.', 'MessageArgs': [''], 'RelatedProperties': ['']}].

This is issue with Ironic used with Kolla Ansible but if we try with Bifrost the image booting goes fine.

Any help or suggestion would be helpful to us.

Best regards,

Ali Hussain