Conversation
|
There's still one problem I don't have a good solution for. After you set the boot order you have to reboot to apply changes. If you change your mind before the reboot it fails to set the values because of the pending request. The first idea is to only apply the last change right before the reboot, which means in case of a failure it fails long time after it was set. And deferring the operation seems also quite complicated, no other function in the project requires this. So not a suitable good approach. Another option is to create a job explicitly instead of issuing the boot order change request. And then delete the job in the job queue by its id (if you change your mind). That's better, but also not ideal. Any thoughts on this? Do we have such a use case? |
How about triggering a reboot after the boot order was changed successfully? |
If reboot is no problem, I'll implement that now. Thank you! |
This would lead to a massive delay during the installation process, not a good idea |
Description
Add new vendor Dell