Issues with redfish trying to set boot device, Not supporting continuous.

This is an issue with 2.70.70.70 FW. Next release will have the fix for this. Mean time can you work with "2.63.60.61" FW.

You can download "2.63.60.61" FW from below link

https://www.dell.com/support/home/ar/en/arbsdt1/drivers/driversdetails?driverid=40t1c&oscode=w12r2&productcode=poweredge-r730xd

Saicb_9,

The reason you're seeing this is that redfish/v1/Systems/System.Embedded.1 API has a setting called BootSourceOverrideEnabled, which if set to Continuous then you can see this error appear. You can either change it from Continuous, or it will be addressed and resolved in the future 2.75.75.75 release.  Unfortunately I do not have any details on any timeframe for its release.

Hope this helps.

Hello Shine,

Thanks for the response I have tries 2.63.60.61 but I am running into another issue 

{"level":"info","ts":1588261420.3526037,"logger":"baremetalhost","msg":"publishing event","reason":"ProvisioningError","message":"Image provisioning failed: Failed to prepare to deploy: Redfish exception occurred. Error: Setting boot mode to bios failed for node 3e500592-a1b4-4345-a35f-aee286d457d3. Error: HTTP PATCH https://x.x.x.x/redfish/v1/Systems/System.Embedded.1 returned code 400. unknown error"}
{"level":"info","ts":1588261420.355495,"logger":"baremetalhost","msg":"stopping on host error","Request.Namespace":"metal3","Request.Name":"bsr22ar07c018","provisioningState":"provisioning","message":"Image provisioning failed: Failed to prepare to deploy: Redfish exception occurred. Error: Setting boot mode to bios failed for node 3e500592-a1b4-4345-a35f-aee286d457d3. Error: HTTP PATCH https://x.x.x.x/redfish/v1/Systems/System.Embedded.1 returned code 400. unknown error"

Can you share Method, URI and Body used to set boot mode using redfish

Hi,

DevOps folks who are facing the set boot mode through iDRAC for Refish (case 1 below) and calling image provisioning from metal3 (case 2), can you please send additional  details by seeting "level":"debug" and share either the tar.gz file or dmsg ouput for us to escalate this for expedite fix?

"llevel":"info"
1. Redfish exception occurred. Error: Setting boot mode to bios failed for node "xyz"
2. stopping on host "xyz" error","Request.Namespace":"metal3","Request.Name":"bsr22ar07c018","provisioningState":"provisioning","message":"Image provisioning failed: Failed to prepare to deploy: Redfish exception occurred. Error: Setting boot mode to bios failed for node

returned code 400. unknown error in both cases

Thanks

pramchan

This seems to solve the issue after setting 

'force_persistent_boot_device': 'Never'

In driver_info. however i have to set up ironic client locally to interact with metal3 ironic api and set the parameter.
this seems to be a reasonable workaround till it is fixed in 2.75.75.75. Thanks guys. Appreciate your help!

Hi Prakash,

Thanks for the workaround but this seems to be random some times though we update the driver_info, somehow it is getting updated back

| driver                 | redfish                                                                  |

| driver_info            | {u'redfish_verify_ca': False, u'redfish_address':                        |

|                        | u'https://*****', u'redfish_username': u'oobAdmin',              |

|                        | u'redfish_password': u'******', u'deploy_kernel':                        |

|                        | u'http://******:6180/images/ironic-python-agent.kernel',            |

|                        | u'deploy_ramdisk': u'http://*****:6180/images/ironic-python-       |

|                        | agent.initramfs', u'redfish_system_id':                                  |

|                        | u'/redfish/v1/Systems/System.Embedded.1'}


The above is ironic node-show after metal3 writes the disk (/dev/sda). in some runs it works fine. I have verified it is applied earlier and node-show did show 

u'force_persistent_boot_device': u'Never'

but for some reason it was gone/updated later.