grub is unable to chainboot from network to SATA drive
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
grub2 (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Machines which are managed by MAAS are configured to always network boot. When an operating system is deployed grub is sent[1] a configuration file which searches drives for recognized boot loaders. When the local disk is a SATA drive this process is not working. The config exits at the end to fallback to booting the next configured device but this config does not always exist(e.g LP:1906379). In that case the deployment fails.
I've verified this happens with grub from Focal(1.
Reproduction:
1. Create a KVM which uses an emulated SATA drive and UEFI firmware.
2. Add the machine and commission it in MAAS
3. Try deploying any operating system. CentOS 8 currently fails to deploy because it does not create a UEFI entry.