Boot order change post deployment

Users
1

In my automation flow, after deploying a Baremetal with MAAS, I currently call the Redfish API to change the boot order so that the system boots from the local disk instead of PXE/MAAS.

Is this step actually necessary? Doesn’t MAAS already handle updating the boot order after deployment (via curtin or other mechanisms)? If MAAS takes care of it, I’d like to avoid making redundant Redfish calls in my workflow.

@r00ta

What’s the best practice here for avoiding unnecessary boot order changes post-deployment?

1 Like
2

Even if the machine is PXE booting MAAS would instruct the machine to boot from the next device, which should be the disk. So there should be no need for you to do anything

1 Like
3

And what if the server was removed from maas?

4

MAAS should set PXE as first boot entry and the disk that contains the root partition as second boot entry.

If you remove the machine entirely from MAAS I’d say it’s up to you to change it accordingly