| 2020-08-26 06:50:35 |
Trent Lloyd |
description |
MAAS currently appears to choose boot devices based on the order they appear in the device list rather than with any logic (someone should perhaps confirm this).
Most server hardware does not support booting from NVMe devices unless they are in UEFI mode, but most hardware also defaults to legacy non-UEFI mode out of the box. This results in an unbootable system after deployment unless the boot device is manually changed in the MAAS UI first.
For Legacy (non-UEFI) systems we should default to a non-NVMe device if one exists to make it more likely we can boot from this device. |
MAAS currently appears to choose boot devices based on the order they appear in the device list rather than with any logic (someone should perhaps confirm this).
Most server hardware does not support booting from NVMe devices unless they are in UEFI mode, but most hardware also defaults to legacy non-UEFI mode out of the box. This results in an unbootable system after deployment unless the boot device is manually changed in the MAAS UI first.
For Legacy (non-UEFI) systems we should default to a non-NVMe device if one exists to make it more likely we can boot from this device.
Triage Request: The requestor of this bug requests that this should be considered a bug rather than a feature request, as it results in systems not being bootable out of the box - and their environment is a bare metal direct-use customer environment (e.g. not orchestrated with some tool that is always modifying the disk layout). |
|
