This bug was fixed in the package livecd-rootfs - 2.525.45
---------------
livecd-rootfs (2.525.45) bionic; urgency=medium
[ Francis Ginther ]
* Use the linux-raspi-hwe-18.04 kernel for raspi3 classic image builds.
(LP: #1889188)
[ Michael Hudson-Doyle ]
* Backport snap seeding and other fixes for live-server ISOs. (LP: #1883156)
* Stop building and mounting the mass-rack and maas-region squashfses for
the server-live build as subiquity does not use them any more.
[ Dimitri John Ledkov ]
* Run snap info on the downloaded snap, rather than against the
store. First of all snap info doesn't have --channel argument, thus
queries the wrong channel, and depening on the cohort, a different
snap might be visible too. Thus seed the base of the snap revision we
dowanloaded, rather than some random one from the store.
* Use snap-tool to seed subiquity snap.
* Subiquity: install linux-firmware in the installer layer, to make
firmware blobs available in the live session. LP: #1847835
[ Robert C Jennings ]
* Fix logic to ensure snapd is seeded in core18-only images (LP: #1871919)
-- Michael Hudson-Doyle <michael.hud...@ubuntu.com> Wed, 22 Jul 2020
14:44:38 +1200
** Changed in: livecd-rootfs (Ubuntu Bionic)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1883156
Title:
bionic-live-server images stuck seeding snapd at early boot
To manage notifications about this bug go to:
https://bugs.launchpad.net/subiquity/+bug/1883156/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
