Extremely slow seeding


#1

If you take the latest live-server bionic installer at http://cdimage.ubuntu.com/ubuntu-server/bionic/daily-live/current/bionic-live-server-amd64.iso and boot it in a VM, the boot is incredibly slow. systemd-analyze blame points the blame squarely at seeding the snaps:

ubuntu-server@ubuntu-server:~$ systemd-analyze blame
     4min 5.272s snapd.seeded.service
    1min 35.377s snapd.hold.service
         40.861s dev-sr0.device
         38.600s dev-loop3.device
         37.384s dev-loop0.device
...

snap changes says this

ubuntu-server@ubuntu-server:~$ snap changes
ID   Status  Spawn                 Ready                 Summary
1    Done    2018-06-13T01:47:31Z  2018-06-13T01:48:58Z  Change configuration of "core" snap
2    Done    2018-06-13T01:48:58Z  2018-06-13T01:51:27Z  Initialize system state
3    Done    2018-06-13T01:48:58Z  2018-06-13T01:49:09Z  Initialize device

and for good measure, here’s snap version:

ubuntu-server@ubuntu-server:~$ snap version
snap    2.32.9+18.04
snapd   2.32.9+18.04
series  16
ubuntu  18.04
kernel  4.15.0-23-generic

Is this some kind of known problem? Is there an ETA on a fix?


#2

snap tasks 2 would have been useful there


#3

I just downloaded the above image (2018-05-29 08:19) and booted it using kvm -m 1500 -snapshot bionic-live-server-amd64.iso and once I got a shell ran systemd-analyze blame | head:

         14.000s snapd.seeded.service
          7.313s console-setup.service
          6.829s dev-sda.device
          6.323s dev-loop0.device
          6.303s snapd.hold.service
          5.614s dev-loop2.device
          5.489s dev-loop3.device
          4.129s networkd-dispatcher.service
          3.414s lxd-containers.service
          2.484s pollinate.service

Any hints what I am missing to reproduce this issue? The output of snap version is the same as for you.


#4

Could it be related to the speed of the CDN when accessed from NZ?


#5

Well aggravatingly in some ways, I rebooted my laptop and the problem went away. Confusing and annoying, but probably not snapd’s fault! Sorry for the noise.