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

[Paride Legovini]

Hi,

While the new livecd-rootfs unblocked the snapd seeding, it seems that
it triggered another problem later in the subiquity install process.

The 20200729.1 bionic-live-server-amd64 image now fails to install
because /media/filesystem/var/lib/snapd/seed/seed.yaml is missing. The
full install logs are attached, however the interesting bits should be
at [1].

The MP [2] with the tentative fix for this bug does touch how seed.yaml
is generated, so the two things are likely to be related.

Big warning: this issue is NOT hit by the by automated ISO test as they
skip the SnapList subiquity step because of [3]. This means that images
are getting promoted but they are to be considered broken.

[1] https://paste.ubuntu.com/p/tYCM4bx6yq/
[2] https://code.launchpad.net/~mwhudson/livecd-rootfs/+git/livecd-rootfs/+merge/387802
[2] https://bugs.launchpad.net/subiquity/+bug/1864868

** Attachment added: "_install_logs.tar.gz"
   https://bugs.launchpad.net/ubuntu-cdimage/+bug/1883156/+attachment/5396961/+files/_install_logs.tar.gz

** Changed in: livecd-rootfs (Ubuntu Bionic)
       Status: Fix Committed => New

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