This bug was fixed in the package ubuntu-fan - 0.12.13

---------------
ubuntu-fan (0.12.13) eoan; urgency=medium

  * d/t/control: Fix missing dependencies for autopkgtests (LP:
#1832238)

 -- Rafael David Tinoco <rafaeldtin...@ubuntu.com>  Mon, 10 Jun 2019
15:41:11 +0000

** Changed in: ubuntu-fan (Ubuntu)
       Status: In Progress => Fix Released

-- 
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/1832238

Title:
  ubuntu-fan autopkgtests depend on undeclared net-tools and bridge-
  utils dependencies

Status in ubuntu-fan package in Ubuntu:
  Fix Released

Bug description:
  
  Whenever running autopkgtests in ubuntu-fan you might hit issues on missing 
dependencies:

  ----

  Starting fanatic-test
  Remapping container filesystem
  lxd test: Waiting for addresses on eth0 ...
  lxd test: Waiting for addresses on eth0 ...
  lxd test: Waiting for addresses on eth0 ...
  lxd test: Waiting for addresses on eth0 ...
  slave: detected primary route through eth0
  slave: DNS: systemd(250.0.1.1)
  test master: ping test (250.0.1.179) ...
  test slave: ping test (250.0.1.1) ...
  test master: ping test ... PASS
  test master: short data test (250.0.1.1 -> 250.0.1.179) ...
  test slave: ping test ... PASS
  test slave: short data test (250.0.1.179 -> 250.0.1.1) ...
  test master: short data ... PASS
  test master: long data test (250.0.1.1 -> 250.0.1.179) ...
  test slave: short data ... PASS
  test slave: long data test (250.0.1.179 -> 250.0.1.1) ...
  test slave: long data ... PASS
  test master: long data ... PASS
  local lxd test: destroying test container ...
  local lxd test: test complete PASS (master=0 slave=0)
  II: Undefining LXD profile for Fan Bridge...
  de-configuring LXD underlay:127.0.0.0/16 overlay:250.0.0.0/8
  Profile fan-250 deleted
  /tmp/autopkgtest.WLlVT9/build.Imn/src/debian/tests/lxd: line 57: ifconfig: 
command not found
  FAIL: No fan-250 left after disable-lxd
  autopkgtest [14:33:37]: test lxd: -----------------------]
  autopkgtest [14:33:37]: test lxd:  - - - - - - - - - - results - - - - - - - 
- - -
  lxd                  FAIL non-zero exit status 1
  autopkgtest [14:33:37]: @@@@@@@@@@@@@@@@@@@@ summary
  docker               FAIL non-zero exit status 1
  lxd                  FAIL non-zero exit status 1
  Exit request sent.

  ----

  autopkgtest [15:24:09]: test lxd: [-----------------------
  /tmp/autopkgtest.7u3mm8/build.s4D/src/debian/tests/lxd: line 3: route: 
command not found
  II: Test LXD...
  master: detected primary route through bridge0
  master: waiting for systemd resolver...
  master: waiting for systemd resolver...
  master: waiting for systemd resolver...
  master: waiting for systemd resolver...
  master: waiting for systemd resolver...
  master: waiting for systemd resolver...
  master: waiting for systemd resolver...
  master: waiting for systemd resolver...
  master: waiting for systemd resolver...
  master: waiting for systemd resolver...
  master: waiting for systemd resolver...
  master: waiting for systemd resolver...
  master: waiting for systemd resolver...
  master: waiting for systemd resolver...
  master: waiting for systemd resolver...
  master: systemd-resolve failure!
  local lxd test: prepare master failed!
  FAIL: Error on LXD test
  autopkgtest [15:24:40]: test lxd: -----------------------]
  autopkgtest [15:24:40]: test lxd:  - - - - - - - - - - results - - - - - - - 
- - -
  lxd                  FAIL non-zero exit status 1

  ----

  That happens because tests don't explicitly declare bridge-utils and
  net-tools as its dependency and the building/autopkgtest environment
  might not have them installed by default.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-fan/+bug/1832238/+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