[Bug 1910557] Autopkgtest regression report (livecd-rootfs/2.408.66)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted livecd-rootfs (2.408.66) for xenial have finished running.
The following regressions have been reported in tests triggered by the package:

ubuntu-image/1.10+16.04ubuntu1 (arm64, i386, s390x, amd64, ppc64el)


Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/xenial/update_excuses.html#livecd-rootfs

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  Buildd images do not launch on macOS under multipass due to missing
  unpacked kernels and initrd

Status in livecd-rootfs package in Ubuntu:
  Fix Released
Status in livecd-rootfs source package in Xenial:
  Fix Committed
Status in livecd-rootfs source package in Bionic:
  Fix Committed
Status in livecd-rootfs source package in Focal:
  Fix Committed
Status in livecd-rootfs source package in Groovy:
  Fix Committed
Status in livecd-rootfs source package in Hirsute:
  Fix Released

Bug description:
  livecd-rootfs v2.700 in hirsute introduced a fix to produce unpacked
  artifacts for use by multipass on macOS hosts. These hosts require
  direct access to a kernel and initrd to boot the buildd images.

  See: https://git.launchpad.net/livecd-
  rootfs/commit/?id=065c82314464fa78337d5122e1d4826a7d6edbb0

  This change needs to be backported to all suites.

  [Impact]

   * Without this change, users are unable to use the buildd images with
  multipass on macOS hosts. Snapcraft utilizes multipass to build snaps,
  so this blocks macOS users from building snaps.

  As a workaround, the CPC team is manually extracting these artifacts
  and publishing them to cloud-images.ubuntu.com. This is not ideal for
  the long-term, and could result in breakage in the event that the CPC
  team forgets to manually publish these artifacts.

  [Test Case]

   * After this change lands, a user should be able to build images with
  the ubuntu-base project and buildd subproject, and the resulting build
  should produce extracted kernel and initrd artifacts.

  [Where problems could occur]

   * These changes are minor, but a mistake could result in broken buildd image hooks (where the build fails) or broken buildd image artifacts (where the images don't work as expected).
  * Since all buildd images are manually tested by the launchpad team, multipass team, and snapcraft team before they enter production, the risk of introducing breakage for end users is low.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1910557/+subscriptions