Deployment fails due to missing EFI directory on system with no EFI support
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Invalid
|
Undecided
|
Unassigned | ||
cloud-init |
Invalid
|
Undecided
|
Unassigned | ||
curtin |
Invalid
|
Undecided
|
Unassigned | ||
maas-cert-server |
Fix Released
|
Critical
|
Unassigned |
Bug Description
Attempting to deploy various versions of Ubuntu via MAAS 2.4.2 (7034-g2f5deb8b
Looking in the system settings, this system does not use EFI at all. It is purely BIOS mode, yet the installer is complaining about a missing efi directory when it fails.
The machine is successfully commissioned, and commissioning does not detect EFI and thus does not create a /boot/efi partition as it is not necessary. Watching the node boot via console, it clearly is doing a BIOS mode PXE boot from the NICs, it is not loading an EFI environment first.
A search and skimming of the manuals for this model (ProLiant SL230s) shows that it has no EFI options available as well:
https:/
https:/
Installation finished. No error reported.
Running command ['udevadm', 'settle'] with allowed return codes [0] (capture=False)
Running command ['umount', '/tmp/tmpmg3cwx
Running command ['umount', '/tmp/tmpmg3cwx
Running command ['umount', '/tmp/tmpmg3cwx
finish: cmd-install/
start: cmd-install/
Finalizing /tmp/tmpmg3cwxp
finish: cmd-install/
curtin: Installation failed with exception: Unexpected error while running command.
Command: ['grep', 'efi', '/proc/mounts']
Exit code: 1
Reason: -
Stdout: ''
Stderr: ''
A full paste of the install lot from the MAAS web ui is here: https:/
And the node's config data from MAAS can be found here:
https:/
Changed in maas-cert-server: | |
status: | Confirmed → Fix Released |
Hi Jeff,
Could you please provide:
1. curtin config (maas <user> machine get-curtin-config <syustem-id>)
2. curtin version
3. Power settings of this machine (maas <user> machine power-parameters <system-id>). I'm interested in the power_boot_type.
Thanks!