bionic-live-server images stuck seeding snapd at early boot
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ubuntu CD Images |
Fix Released
|
Undecided
|
Unassigned | ||
subiquity |
Invalid
|
Undecided
|
Unassigned | ||
livecd-rootfs (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Bionic |
Fix Released
|
High
|
Michael Hudson-Doyle |
Bug Description
[impact]
The bionic-
kvm -m 2048 -boot d -cdrom ./bionic-
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.
Changed in livecd-rootfs (Ubuntu Bionic): | |
milestone: | none → ubuntu-18.04.5 |
tags: | added: id-5f15f568604db45e7b7e52cf |
Changed in subiquity: | |
status: | New → Invalid |
description: | updated |
tags: |
added: verification-done verification-done-bionic removed: verification-needed verification-needed-bionic |
Changed in ubuntu-cdimage: | |
status: | New → Fix Released |
I wonder if this is because subiquity & lxd have switched to core18 base.