[Bug 1923268] Re: grubnet default grub.cfg should try /grub/grub.cfg-${net_default_mac} before /grub/grub.cfg

[dann frazier]

Understood, and I see you already covered that above. What I don't
follow is what caused MAAS enlistment of ARM to break. I mean, it used
to work fine. From reading the tea leaves here, was it that MAAS
switched from generating its own grubnet image w/ a built-in grub.cfg to
a signed (and therefore immutable) grubnet?

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to grub2-signed in Ubuntu.
https://bugs.launchpad.net/bugs/1923268

Title:
  grubnet default grub.cfg should try /grub/grub.cfg-${net_default_mac}
  before /grub/grub.cfg

Status in MAAS:
  New
Status in grub2-signed package in Ubuntu:
  Confirmed

Bug description:
  MAAS uses the signed network GRUB bootloader when a machine network
  boots on AMD64 and ARM64. The configuration MAAS produces depends on
  the machine which are identified by MAC address. The default grub.cfg
  in the boot loader downloads /grub/grub.cfg from the remote host. As
  that doesn't provide the MAC address MAAS provides a default
  configuration file:

  configfile /grub/grub.cfg-${net_default_mac}
  configfile /grub/grub.cfg-default-amd64

  There are two issues with this:

  1. This causes an additional unnecessary request.
  2. It is assumed an known machine is amd64.

  Can the default grub.cfg embedded in grubnet<arch>.efi be updated to

  configfile /grub/grub.cfg-${net_default_mac}
  configfile /grub/grub.cfg-default-<ARCH>
  configfile /grub/grub.cfg

  This would be similar to what PXELinux[1] does.

  [1] https://wiki.syslinux.org/wiki/index.php?title=PXELINUX

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1923268/+subscriptions