| 2020-12-01 09:44:49 |
Lee Trager |
description |
When MAAS deploys CentOS 7/8 it boots into the user selected commissioning environment(Xenial, Bionic, or Focal) and runs Curtin. If the system uses UEFI Curtin creates a boot entry with efibootmgr. Adding and ordering the entry is logged and I have manually confirmed it is created properly. Once Ubuntu shuts down to boot into the deployed system it seems to be removing CentOS's UEFI boot entry. I have confirmed this happens during the shutdown process by using the system firmware to select a temporary boot device(Ubuntu LiveCD) and running efibootmgr -v to see only the system default boot entries.
This can cause booting failures when network booting isn't available or a grub bug such as LP:1906344. |
When MAAS deploys CentOS 7/8 it boots into the user selected commissioning environment(Xenial, Bionic, or Focal) and runs Curtin. If the system uses UEFI Curtin creates a boot entry with efibootmgr. Adding and ordering the entry is logged and I have manually confirmed it is created properly. Once Ubuntu shuts down to boot into the deployed system it seems to be removing CentOS's UEFI boot entry. I have confirmed this happens during the shutdown process by using the system firmware to select a temporary boot device(Ubuntu LiveCD) and running efibootmgr -v to see only the system default boot entries.
This can cause booting failures when network booting isn't available or a grub bug such as LP:1906344.
Reproduction:
1. Deploy CentOS 7 or 8 using MAAS to a UEFI system.
2. Verify UEFI boot entry was added in installation/Curtin log
3. In deployed system or rescue environment see `efibootmgr -v` does not include CentOS. |
|
