[Bug 2049723] Re: ubuntu-server ftbfs in jammy with livecd-rootfs 2.765.34

[Steve Langasek]

Hello Steve, or anyone else affected,

Accepted livecd-rootfs into jammy-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/livecd-
rootfs/2.765.38 in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
jammy to verification-done-jammy. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-jammy. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: livecd-rootfs (Ubuntu Jammy)
       Status: Triaged => Fix Committed

** Tags added: verification-needed verification-needed-jammy

-- 
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/2049723

Title:
  ubuntu-server ftbfs in jammy with livecd-rootfs 2.765.34

Status in livecd-rootfs package in Ubuntu:
  Fix Released
Status in livecd-rootfs source package in Jammy:
  Fix Committed
Status in livecd-rootfs source package in Mantic:
  Won't Fix
Status in livecd-rootfs source package in Noble:
  Fix Released

Bug description:
  [Impact]
  ========

  There's a step in the `ubutu-server` `live` image builds which call
  `unminimize`.

  With changes introduced in LP: #2036725 `unminimize` now calls `lxd`
  which on a minimized build/instance will install the lxd snap using the
  logic in the `lxd` shim from lxd-installer. Previously `unminimize` used `snap`
  directly to install the `lxd` snap and `ubutu-server` `live` image builds diverted `snap` to allow for calling `unminimize` without the snap install step.

  This change breaks the `ubuntu-server` `live` image builds.

  [Test Plan]
  ===========

  1. Test build of ubuntu-server images with PROPOSED=1 enabled succeed
  (they have currently been failing for > 1 week)

  [Where Problems Could Occur]
  =============================

  One change we do not want is that the lxd snap is not installed at the
  stage of calling `unminimize`. We need to ensure this is not the case.

  [OG Bug Report]
  ===============

  NEEDRESTART-VER: 3.5
  Invoking LXD so that it can be installed by the lxd-installer's script..
  Traceback (most recent call last):
    File "<string>", line 1, in <module>
  FileNotFoundError: [Errno 2] No such file or directory
  /sbin/lxd: 6: exec: /snap/bin/lxd: not found
  E: config/hooks/01-unminimize.chroot_early failed (exit non-zero). You should check for errors.
  P: Begin unmounting filesystems...

  https://launchpad.net/~ubuntu-cdimage/+livefs/ubuntu/jammy/ubuntu-
  server-live/+build/566145

  This is an unminimized image build.

  The change that broke this was introduced for LP: #2036725.

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