MAAS 3.5.4 changes host boot order as a part of deployment

Users
1

When deploying a host using the web UI, MAAS changes the boot order of the host. The original boot order prioritized PXE over the local disk. After deployment, the boot order prioritizes local disk over network adapters. A quick search reveals that this is done to avoid infinite PXE loops.

The trouble we run into is after releasing & deploying the same host, it doesn’t PXE because local disk is still prioritized over network adapters. It seems reasonable that if MAAS changes the boot order on deployment, should it change the boot order upon release to resolve this issue? Otherwise, I’m curious how others are solving this problem.

Name  Version                  Rev    Tracking    Publisher   Notes
maas  3.5.4-16349-g.4dbbed5f4  38907  3.5/stable  canonical✓  held
2

It depends on the power driver you use. If you use IPMI or redfish MAAS will ask the machine to pxe boot it is powered on

3

Hey, Jocopo. Thank you for responding. We use the IPMI power driver across our fleet. As far as I know, the machine never tries to PXE after a release and deploy.

Is this something that was implemented in a later version of MAAS? Is this process logged anywhere? It would be very helpful if it would PXE boot as a part of this process. As for now, we have to manually change the boot order to ensure that the deployment takes place.

4

It’s been there since MAAS 2.x, maybe your BMC is misbehaving? You can try to make the same requests manually to your BMC and debug it maas/src/provisioningserver/drivers/power/ipmi.py at 93dc3e54165e5935179bf8e5a032998fd041881a · canonical/maas · GitHub

5

Hey, Jocopo. Thank you for pointing me ipmi code within the MAAS repo. I’ll spend some time debugging this and get back to you.