Failed to release machine running ESXi

Bug #2066984 reported by maasuser1
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MAAS
Invalid
Undecided
Unassigned

Bug Description

I got a Supermicro machine running ESXi 8.0U2 managed by MAAS. When I `release` it, it just reboots to ESXi instead of performing PXE. i.e. MAAS failed to boot this device into the network boot mode.

Revision history for this message
Jacopo Rota (r00ta) wrote :

Please provide all the rackd logs and ensure the machine is properly configured to pxe first

Changed in maas:
status: New → Incomplete
Revision history for this message
maasuser1 (maasuser1) wrote :

Hi Jacopo, I understood the manual workaround. But according to IPMI 2.`0 specs:

> The system should attempt to boot from the specified device instance first. If the boot fails the system should attempt booting using the system's boot order configuration.

https://www.intel.com/content/dam/www/public/us/en/documents/product-briefs/ipmi-second-gen-interface-spec-v2-rev1-1.pdf#page=416.71

I think MAAS is supposed to boot the machine into PXE env.

Revision history for this message
Jacopo Rota (r00ta) wrote :

what's the boot order of the machine?

Revision history for this message
Jacopo Rota (r00ta) wrote :

also, if the machine has been released and it's in the Ready state, if you power on the machine what you would expect to happen?

Revision history for this message
maasuser1 (maasuser1) wrote :

> what's the boot order of the machine?

#1: UEFI Hard Disk (ESXi)
#2: UEFI Network PXE

> if the machine has been released and it's in the Ready state, if you power on the machine what you would expect to happen?

Dry run into PXE env handled by MAAS, then shutdown.

--

My point is that when it performs the "release" process, in general, such API provided by IPMI/Redfish allows MAAS to instruct the machine to boot into the PXE env, i.e. temporary boot option override. However, this doesn't work as expected on this machine with ESXi deployed.

Revision history for this message
Jacopo Rota (r00ta) wrote :

> My point is that when it performs the "release" process, in general, such API provided by IPMI/Redfish allows MAAS to instruct the machine to boot into the PXE env, i.e. temporary boot option override. However, this doesn't work as expected on this machine with ESXi deployed.

This is in general a wrong expectation. By design the machines must always PXE first. MAAS will then decide what to do with the machine depending on the status of the machine.

MAAS is only changing the boot order for the hmcz power driver.

I'm marking this as invalid then

Changed in maas:
status: Incomplete → Invalid
Revision history for this message
maasuser1 (maasuser1) wrote :

Thanks, Jacopo.
May I ask why not MAAS run IPMItool to change the boot order for IPMI-capable machines, but only process this for IBM Z?

Revision history for this message
Jacopo Rota (r00ta) wrote :

Because some BMC do not allow you to change the boot order with IPMI

Revision history for this message
maasuser1 (maasuser1) wrote :

Thank you!

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.