[Bug 1883156] Re: bionic-live-server images stuck seeding snapd at early boot

[Dimitri John Ledkov]

One option is to fix subiquity to not assume that filesystem has
anything seeded.

Another option is to provide an empty seed.yaml in the filesystem layer.

Or seed something into the filesystem layer.

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

Title:
  bionic-live-server images stuck seeding snapd at early boot

Status in subiquity:
  Invalid
Status in Ubuntu CD Images:
  New
Status in livecd-rootfs package in Ubuntu:
  Fix Released
Status in livecd-rootfs source package in Bionic:
  New

Bug description:
  [impact]
  The bionic-live-server-amd64 images get stuck at early boot of the installer system waiting for snapd to be seeded. The seeding never happens. The problem can be easily reproduced by running:

    kvm -m 2048 -boot d -cdrom ./bionic-live-server-amd64.iso

  on a recent pending image. I just tested it with:

  Ubuntu-Server 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200610)

  Note that the problem happens early, before subiquity sets up the
  network, so I don't think it's a problem accessing the store.

  [test case]
  boot the live server ISO successfully

  [regression potential]
  We should check that we don't regress the other flavours that seed snaps: ubuntu desktop, budge and mate. I think the seed.yaml in the main squashfs will be unchanged, which will be easy to check.

To manage notifications about this bug go to:
https://bugs.launchpad.net/subiquity/+bug/1883156/+subscriptions