Running autopkgtest-build-lxd images:ubuntu/bionic/amd64 results in:
Creating autopkgtest-prepare-1ay
Starting autopkgtest-prepare-1ay
Container finished booting. Distribution Ubuntu, release bionic,
architecture amd64
Running setup script /usr/share/autopkgtest/setup-commands/setup-testbed...
grep: //etc/network/interfaces: No such file or directory
Err:1 http://archive.ubuntu.com/ubuntu bionic InRelease
Temporary failure resolving 'archive.ubuntu.com'
Err:2 http://archive.ubuntu.com/ubuntu bionic-updates InRelease
Temporary failure resolving 'archive.ubuntu.com'
Reading package lists...
W: Failed to fetch
http://archive.ubuntu.com/ubuntu/dists/bionic/InRelease Temporary
failure resolving 'archive.ubuntu.com'
W: Failed to fetch
http://archive.ubuntu.com/ubuntu/dists/bionic-updates/InRelease
Temporary failure resolving 'archive.ubuntu.com'
W: Some index files failed to download. They have been ignored, or old
ones used instead.
Reading package lists...
Building dependency tree...
Reading state information...
dbus is already the newest version (1.12.2-1ubuntu1).
The following NEW packages will be installed:
eatmydata libeatmydata1
0 upgraded, 2 newly installed, 0 to remove and 0 not upgraded.
Need to get 12.1 kB of archives.
After this operation, 54.3 kB of additional disk space will be used.
Err:1 http://archive.ubuntu.com/ubuntu bionic/main amd64 libeatmydata1
amd64 105-5
Temporary failure resolving 'archive.ubuntu.com'
Err:2 http://archive.ubuntu.com/ubuntu bionic/main amd64 eatmydata all 105-5
Temporary failure resolving 'archive.ubuntu.com'
E: Failed to fetch
http://archive.ubuntu.com/ubuntu/pool/main/libe/libeatmydata/libeatmydata1_105-5_amd64.deb
Temporary failure resolving 'archive.ubuntu.com'
E: Failed to fetch
http://archive.ubuntu.com/ubuntu/pool/main/libe/libeatmydata/eatmydata_105-5_all.deb
Temporary failure resolving 'archive.ubuntu.com'
E: Unable to fetch some archives, maybe run apt-get update or try with
--fix-missing?
because the networking on artful/bionic is slow to start, and 'apt-get update' returns success though it's actually failing.
I propose to add a check for the default network route to the "is the container up?" polling loop:
https:/