[Bug 2034253] Re: Jammy buildd image doesn't boot because grub is installed to \EFI\debian instead of \EFI\ubuntu

[Steve Langasek]

The path on the ESP is constructed from GRUB_DISTRIBUTOR, which in
/etc/default/grub is set to:

GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`

So first, 'Debian' is not a reasonable fallback on Ubuntu.  The fallback
should be Ubuntu.

And second, the lsb-release package is not guaranteed to be installed
whenever grub-install is called, because grub2-common does not depend on
it.  It's part of the minimal seed, but the buildd images don't use the
minimal seed; they subset it.

Rather than depending on lsb-release, however, we should just change
this to use the not-deprecated /etc/os-release interface, e.g.:

GRUB_DISTRIBUTOR=`. /etc/os-release && echo $NAME || echo Ubuntu`

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

Title:
  Jammy buildd image doesn't boot because grub is installed to
  \EFI\debian instead of \EFI\ubuntu

Status in cloud-images:
  Confirmed
Status in grub2 package in Ubuntu:
  New
Status in livecd-rootfs package in Ubuntu:
  Confirmed

Bug description:
  Recent Jammy buildd images fail to boot (since at least September 1st:
  https://github.com/canonical/craft-
  application/actions/runs/6016993725/job/16424264050?pr=64).

  Trying to run an image from https://cloud-
  images.ubuntu.com/buildd/daily/jammy/current in QEMU, only gets me a
  GRUB prompt. Multipass and Snapcraft consequently fail to work with
  these images.

  I haven't checked other image series.

  This is similar to https://bugs.launchpad.net/cloud-
  images/+bug/2027686, but a new issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/2034253/+subscriptions