Long snapd seeding time without network

Bug #1824401 reported by Andreas Hasenack on 2019-04-11
This bug affects 1 person
Affects Status Importance Assigned to Milestone

Bug Description

When starting an install, the boot messages scroll by, some FAILED ("Create System Users" IIRC, at the very beginning), most green. Then it all stops and waits for snapd to "seed". This takes dozens of seconds. At first I thought it was related to the installation being done in a VM, but I later tried on actual hardware (i7, 16Gb RAM, intel SSD, T420 laptop) and it was also stuck there for about 50s. Then finally the installer started.

UPDATE: this vm had no network, as I was testing the offline installation case. With a network, this time drops to about 14s. But note that in the laptop case with just a wifi network, it again will take a very long time, because wifi is not configured yet.

This is on a VM, it waited more than 52s

summary: - snapd seeding time
+ Long snapd seeding time
summary: - Long snapd seeding time
+ Long snapd seeding time without network
description: updated
Michael Hudson-Doyle (mwhudson) wrote :

Snap seeding is very slow yes. I don't think there's anything subiquity can do about this (except maybe slimming down the snap might help a very little bit).

Changed in subiquity:
status: New → Invalid
Michael Vogt (mvo) wrote :

The output of "systemd-analyze blame" and "snap debug timings <chg-id>" (where <chg-id> is the id of the change that did all the seeding (available via snap changes)).

Michael Hudson-Doyle (mwhudson) wrote :

Attaching a tarball with all that and a bit more. There are some other delays in the boot that are not related to snapd, it seems, which should probably be the subject of other bugs.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers