Comment 3 for bug 2034253

Revision history for this message
John Chittum (jchittum) wrote : Re: Jammy buildd image doesn't boot

pinpointed to `livecd-rootfs` release 2.765.22 on Jammy:

Drop use of --removable flag to grub-install from
    live-build/buildd/hooks/02-disk-image-uefi.binary, to match the cloud
    images (7c760864fdcb278ca37396f06f5e3f297428d63d). This fixes
    bootloader updates in the buildd images, but also fixes compatibility
    with using devtmpfs for losetup.

https://git.launchpad.net/livecd-rootfs/commit/?h=ubuntu/jammy&id=5ac4df3a1a928b76e00c74647ad9d0fe30c007e7

this was revered in `ubuntu/master` earlier because it caused images to fail to boot. for completeness, i did try a few different configurations in the code block to see if things could work

1. full-revert of the commit. This worked
2. Deleted just the `--removable` line. This caused it to fail to boot
3. kept `--removable` but deleted the if statement with `boot/efi`. this failed to boot

I'm building livecd-rootfs package now, and will try to run a launchpad build with it as well. The big issue here is that vorlon noticed an issue with livecd-rootfs builders, and issues related to buildd. I have successful builds before the merge in, within a single day, so it appears the launchpad-builder issue isn't affecting being able to build `buildd` on 22.04 as of 20230827.