*** This bug is a duplicate of bug 1732739 ***
https://bugs.launchpad.net/bugs/1732739
** Tags removed: verification-failed-xenial verification-needed
verification-needed-zesty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
*** This bug is a duplicate of bug 1732739 ***
https://bugs.launchpad.net/bugs/1732739
Event though both test failures where triggered by the change from
ifupdown to systemd-networkd/resolvd the reasons for the problems are
completely different. For lxd the problem is in the dep8 test script.
On Wed, Nov 15, 2017 at 09:32:18AM -, Stefan Bader wrote:
> @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
@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
The britney hint was bumped for ubuntu-fan to override the failing
autopkgtests. Which means this bug was automatically marked as closed
by the migration of a version of the package that still had failing
autopkgtests. Reopening.
** Changed in: ubuntu-fan (Ubuntu)
Status: Fix Released =>
I don't understand why this was SRUed to xenial, where we do not use
systemd-networkd / systemd-resolved; and there is no SRU test case
listed in the bug. Łukasz, why was this accepted and what do you expect
for testing?
** Tags removed: verification-needed-xenial
** Tags added:
** Tags added: verification-needed verification-needed-zesty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1718548
Title:
ubuntu-fan autopkgtests are broken against systemd-resolved
To manage
** Changed in: ubuntu-fan (Ubuntu Xenial)
Importance: Undecided => Medium
** Changed in: ubuntu-fan (Ubuntu Xenial)
Status: New => In Progress
** Changed in: ubuntu-fan (Ubuntu Xenial)
Assignee: (unassigned) => Stefan Bader (smb)
** Changed in: ubuntu-fan (Ubuntu Zesty)
This bug was fixed in the package ubuntu-fan - 0.12.6
---
ubuntu-fan (0.12.6) artful; urgency=medium
* fanatic: Add short success delay to nc_send (LP: #1721352)
* fanatic: Catch test preparation steps failing (LP: #1718548)
* fanatic: Add DNS checks to local-test preparation
** Also affects: ubuntu-fan (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: ubuntu-fan (Ubuntu Zesty)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I could not see the docker failure when running a local ADT test. So I
added the checking with some additional output to see what is going on.
The latest test failure (at least now it is detected quickly)
http://autopkgtest.ubuntu.com/packages/u/ubuntu-fan/artful/amd64 shows
that the host side is
** Changed in: ubuntu-fan (Ubuntu)
Importance: Undecided => High
** Changed in: ubuntu-fan (Ubuntu)
Status: New => In Progress
** Changed in: ubuntu-fan (Ubuntu)
Assignee: (unassigned) => Stefan Bader (smb)
--
You received this bug notification because you are a member of Ubuntu
Ok, I get the drift, but frankly when systemd-resolvd/systemd-networkd
change the startup timing that drastically I guess fan tests failing
might be the least of our problems...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Attached is the partial patch, which should also provide insight into
how to fix the docker test.
** Patch added: "ubuntu-fan-resolved.debdiff"
https://bugs.launchpad.net/ubuntu/+source/ubuntu-fan/+bug/1718548/+attachment/4954044/+files/ubuntu-fan-resolved.debdiff
--
You received this bug
14 matches
Mail list logo
