Customer attempted to install baremetal cluster on HP ProLiant DL360 Gen10 hardware running iLO5 v3.08. The cluster install status was hanging on baremetalhost:cp0: inspecting. 

The status of the baremetal resource was: 'Failed to inspect hardware. Reason: unable to start inspection: Redfish exception occurred. Error: Setting boot mode to uefi failed for node 813b617e-42f9-48db-99e9-1b2f3a35f94b. Error: HTTP PATCH https://10.64.143.135/redfish/v1/Systems/1 returned code 400. iLO.0.10.ExtendedInfo: See @Message.ExtendedInfo for more information. Extended information: [{''MessageId'': ''iLO.2.24.UnsupportedOperation''}]'     

They tried the workaround to manually set the BIOS mode to UEFI first on each node before running the installer (here’s a Bugzilla bug for it https://bugzilla.redhat.com/show_bug.cgi?id=1820337) which says it is resolved but they would like to check if it was tested using a hardware that already had the mode set to UEFI. 

HPE support advised customer that ilo API endpoint is READONLY and does not work in any version of ILO5 because ILO 5 implements `BootSourceOverrideMode` as a read-only item that reflects the current boot mode. 
Reference: https://servermanagementportal.ext.hpe.com/docs/redfishservices/ilos/ilo5/ilo5_adaptation/#boot-source-override 

Slack discussion: https://redhat-internal.slack.com/archives/CFP6ST0A3/p1734579771973629