[Bug 1952093] Re: Seeded snaps broken in the Focal dailies

[Michael Hudson-Doyle]

** Also affects: livecd-rootfs (Ubuntu Focal)
   Importance: Undecided
       Status: New

** Description changed:

+ [impact]
  In the recent focal-live-server-amd64 dailies, e.g. in:
  
  Ubuntu-Server 20.04.3 LTS "Focal Fossa" - Release amd64 (20211124)
  
  some snap related errors are printed to the terminal at boot time, and
  then subiquity doesn't start. Jumping to tty2 and doing a simple
  
-   systemctl status snapd
+   systemctl status snapd
  
  shows that snapd complains about the state of the core18 snap, and
  indeed /snap/core18/current/ is empty. Reinstalling core18 and
  refreshing subiquity from the candidate channel makes it start normally.
  This looks like a problem in the snap seeding.
+ 
+ This turns out to be because the core18_*.snap file is missing from the
+ live layer, thanks to some over enthusiastic cleanup in a livecd-rootfs
+ hook.
+ 
+ [test case]
+ build a focal live-server iso with livecd-rootfs. check it boots.
+ 
+ [regression potential]
+ the fix touches a hook that only runs for live-server builds, so even if buggy it can't really make things worse (as current ISOs are basically inoperable)

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

Title:
  Seeded snaps broken in the Focal dailies

Status in livecd-rootfs package in Ubuntu:
  New
Status in livecd-rootfs source package in Focal:
  New

Bug description:
  [impact]
  In the recent focal-live-server-amd64 dailies, e.g. in:

  Ubuntu-Server 20.04.3 LTS "Focal Fossa" - Release amd64 (20211124)

  some snap related errors are printed to the terminal at boot time, and
  then subiquity doesn't start. Jumping to tty2 and doing a simple

    systemctl status snapd

  shows that snapd complains about the state of the core18 snap, and
  indeed /snap/core18/current/ is empty. Reinstalling core18 and
  refreshing subiquity from the candidate channel makes it start
  normally. This looks like a problem in the snap seeding.

  This turns out to be because the core18_*.snap file is missing from
  the live layer, thanks to some over enthusiastic cleanup in a livecd-
  rootfs hook.

  [test case]
  build a focal live-server iso with livecd-rootfs. check it boots.

  [regression potential]
  the fix touches a hook that only runs for live-server builds, so even if buggy it can't really make things worse (as current ISOs are basically inoperable)

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