subiquity

subiquity & console-conf should block on snapd seeding to complete

Bug #1863887 reported by Dimitri John Ledkov
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
subiquity
New
Undecided
Unassigned
livecd-rootfs (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

subiquity & console-conf should block on snapd seeding to complete

Such that snapd is available before getty.target starts.

Tags: core20
Revision history for this message
Michael Hudson-Doyle (mwhudson) wrote :

The subiquity service unit doesn't even exist until seeding is completed, no?

Revision history for this message
Michael Hudson-Doyle (mwhudson) wrote :

subiquity end of this needs fixing in the image build

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package livecd-rootfs - 2.651

---------------
livecd-rootfs (2.651) focal; urgency=medium

  * Do not start subiquity until cloud-final and snapd.seeded have
    completed. (LP: #1863887)

 -- Michael Hudson-Doyle <email address hidden> Fri, 06 Mar 2020 17:07:37 +0100

Changed in livecd-rootfs (Ubuntu):
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.