@Steve, we try to get the code base of Fan synced across releases (one
part of the reasons is that docker and lxd may backport things at any
time, the other part is to avoid having to maintain subtly different
code bases). The changes I attributed to this bug are an additional exit
in an awk script which is verified by the tests still working. The other
part is adding tests and print statements for DNS configuration (host
and container side) which can be verified by looking at the test logs.

As for the docker tests failing, we probably should move that to its own bug. 
Right now this only happens in the CI environment and I cannot see much that 
the Fan testing could do:
- the hosting VM (artful/bionic) is using netplan and from print statements
  has systemd-resolv ready before launching the container
- the container (docker) uses its own DNS resolver, we pull latest lts images so
  those are xenial based atm.
- the image is pulled by dockerd, so that has at least DNS resolution for the
  proxy
- however inside the container (and unfortunately that is rather limited in the
  supplied commands) DNS lookups via the docker resolver fail.

I can pull the current cloud-images used by adt locally and get all
testing passed without the slightest issue.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to ubuntu-fan in Ubuntu.
https://bugs.launchpad.net/bugs/1718548

Title:
  ubuntu-fan autopkgtests are broken against systemd-resolved

Status in ubuntu-fan package in Ubuntu:
  Triaged
Status in ubuntu-fan source package in Xenial:
  Fix Committed
Status in ubuntu-fan source package in Zesty:
  Fix Committed

Bug description:
  Now that 17.10 has migrated to netplan+systemd-networkd+systemd-
  resolved by default, ubuntu-fan autopkgtests are failing; at least one
  reason for this failure is wrong detection of the default network
  interface because autopkgtest environments appear for some reason to
  be getting multiple default routes:

  autopkgtest [20:14:59]: test lxd: [-----------------------
  Error: either "dev" is duplicate, or "ens2" is a garbage.
  II: Auto-init LXD...
  LXD has been successfully configured.
  II: Creating Fan Bridge...
  /usr/sbin/fanatic: .0.0/16: unknown underlay network format
  FAIL: Error on enable-fan
  autopkgtest [20:15:10]: test lxd: -----------------------]

  
(https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-artful/artful/amd64/u/ubuntu-
  fan/20170916_203221_4f037@/log.gz)

  The other part failure appears to be a race with systemd-resolved in
  setting up the network inside of docker containers:

  autopkgtest [17:25:39]: test docker: [-----------------------
  Running in the Canonical CI environment
  II: Auto-create Fan Bridge...
  configuring fan underlay:10.220.0.0/16 overlay:250.0.0.0/8
  II: Create docker Fan Network...
  configuring docker for underlay:10.220.0.0/16 overlay:250.0.0.0/8 (fan-250 
250.4
  6.84.0/24)
  1c8a03aa50ab88b997c3b3aee88bfa6933b14368f1594db4a800c2ae8d62074f
  II: Test docker...
  local docker test: pulling container images ...
  Using default tag: latest
  latest: Pulling from library/ubuntu
  d5c6f90da05d: Pulling fs layer
  [...]
  2b8db33536d4: Pull complete
  Digest: 
sha256:2b9285d3e340ae9d4297f83fed6a9563493945935fc787e98cc32a69f5687641
  Status: Downloaded newer image for ubuntu:latest
  local docker test: creating test container ...
  5cbdd232b71bc0738f27f1fa3eae4360716bfe3f8cea976874bf6309b1843169
   slave: installing ping ...
  W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/xenial/InRelease  
Temporary failure resolving 'archive.ubuntu.com'
  [...]
  E: Unable to locate package iputils-ping
   slave: installing nc ...
  E: Unable to locate package netcat-openbsd
  test master: ping test (250.46.84.2) ...
  test slave: ping test (250.46.84.1) ...
  test slave: ping test ... FAIL
  --- transcript start ---
  /bin/sh: 108: ping: not found
  --- transcript end ---
  test slave: short data test (250.46.84.2 -> 250.46.84.1) ...
  test master: ping test ... PASS
  test master: short data test (250.46.84.1 -> 250.46.84.2) ...
  autopkgtest [20:12:19]: ERROR: timed out on command [...]

  I've reproduced this problem locally and prepared a partial patch
  based on a similar fix to the docker.io package's autopkgtests - but
  so far this only fixes races in the lxd test, not in the docker test,
  so it needs further investigation.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-fan/+bug/1718548/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to     : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to