[Bug 1878225] Re: Please remove lxd.snap from lxd images, as it fails to seed thus failing the first boot - snapd.seeded.service waits forever (?) to have snaps seeded in LXD on s390x and arm64

[Balint Reczey]

@stgraber I'd fully agree if snapd.seeded timed out after a few minutes,
but I have a container where snapd.seeded.service is running for 49 days
keeping the system in a starting state.

While this problem may not occur only with snapd, but the snapd package
plays an important enough role in the software stack around Ubuntu to be
fixed.

I agree that autopkgtest network should reject rather than drop packets because the assumption in autopkgtests is having Internet access. From https://people.debian.org/~mpitt/autopkgtest/README.package-tests.html:
...
Network access

autopkgtest needs access to the network at least for downloading test
dependencies and possibly dist-upgrading testbeds. In environments with
restricted internet access you need to set up an apt proxy and configure
the testbed to use it. (Note that the standard tools like autopkgtest-
build-lxc or mk-sbuild automatically use the apt proxy from the host
system.)

In general, tests are also allowed to access the internet. As this
usually makes tests less reliable, this should be kept to a minimum; but
for many packages their main purpose is to interact with remote web
services and thus their testing should actually cover those too, to
ensure that the distribution package keeps working with their
corresponding web service.

Debian's production CI infrastructure allows unrestricted network access, in Ubuntu's infrastructure access to sites other than *.ubuntu.com and *.launchpad.net happens via a proxy (limited to DNS and http/https).
....

By having a stricter network setup in Ubuntu we are set up for facing
failures time to time and rejecting packets at least speed up those
failures.

Autopkgtest can also be fixed to set up proxy for snaps.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to autopkgtest in Ubuntu.
https://bugs.launchpad.net/bugs/1878225

Title:
  Please remove lxd.snap from lxd images, as it fails to seed thus
  failing the first boot - snapd.seeded.service waits forever (?) to
  have snaps seeded in LXD on s390x and arm64

Status in Auto Package Testing:
  Triaged
Status in cloud-images:
  Invalid
Status in snapd:
  New
Status in autopkgtest package in Ubuntu:
  Triaged
Status in lxd package in Ubuntu:
  Invalid
Status in snapd package in Ubuntu:
  Invalid

Bug description:
  lxc launch ubuntu-daily:groovy gg-test
  lxc shell gg-test
  root at gg-test:~# service snapd.seeded status
  ● snapd.seeded.service - Wait until snapd is fully seeded
       Loaded: loaded (/lib/systemd/system/snapd.seeded.service; enabled; vendor preset: enabled)
       Active: activating (start) since Tue 2020-05-12 14:14:52 UTC; 30min ago
     Main PID: 249 (snap)
        Tasks: 10 (limit: 4704)
       Memory: 11.3M
       CGroup: /system.slice/snapd.seeded.service
               └─249 /usr/bin/snap wait system seed.loaded

  May 12 14:14:52 gg-test systemd[1]: Starting Wait until snapd is fully
  seeded...

  root at gg-test:~# systemctl list-jobs 
  JOB UNIT                                 TYPE  STATE  
  132 systemd-update-utmp-runlevel.service start waiting
  119 cloud-config.service                 start waiting
  122 snapd.seeded.service                 start running
  2   multi-user.target                    start waiting
  115 cloud-init.target                    start waiting
  1   graphical.target                     start waiting
  138 snapd.autoimport.service             start waiting
  121 cloud-final.service                  start waiting

  8 jobs listed.

  root at gg-test:~# journalctl -a | pastebinit
  https://paste.ubuntu.com/p/PtdcvvdKCM/

To manage notifications about this bug go to:
https://bugs.launchpad.net/auto-package-testing/+bug/1878225/+subscriptions