This bug was fixed in the package systemd - 232-21ubuntu3
---
systemd (232-21ubuntu3) zesty; urgency=medium
[ Martin Pitt ]
* resolved: Disable DNSSEC by default on stretch and zesty.
Both Debian stretch and Ubuntu zesty are close to releasing, switch to
DNSSEC=off by
This bug was fixed in the package systemd - 232-21ubuntu3
---
systemd (232-21ubuntu3) zesty; urgency=medium
[ Martin Pitt ]
* resolved: Disable DNSSEC by default on stretch and zesty.
Both Debian stretch and Ubuntu zesty are close to releasing, switch to
DNSSEC=off by
Confirmed that the test in the 232-21ubuntu3 source package no longer
hangs.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
Hello Seth, or anyone else affected,
Accepted systemd into zesty-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/systemd/232-21ubuntu3
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
** Description changed:
+ [Impact]
+
+ * Due to upgraded netcat in zesty, ADT testcase 12 started to hang upon
calls to netcat.
+ * The upgraded netcat changed default behaviour from -q0 (quit straight
away) to -q-1 (wait infinity)
+ * Proposed fix is an upstream cherry-pick to add a `-w1`
** Also affects: systemd (Ubuntu Zesty)
Importance: Undecided
Status: New
** Changed in: systemd (Ubuntu Zesty)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
We think it's that the nc calls in this test need -q0, and that it
started with a netcat-openbsd upload that changed this default.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
It does seem to be something in zesty. Not in the kernel though, I tried
xenial and yakkety kernels with zesty userspace and still got the hang.
But when I use a zesty kernel with yakkety userspace I don't see it.
--
You received this bug notification because you are a member of Ubuntu
Touch
BTW, I tested the systemd package from zesty on yakkety (including
rebuilding it) and the tests passed, so it seems to be that something in
zesty causes this test failure.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
The cause seems to be that TEST-12-ISSUE-3171 is hanging. I've
reproduced the problem with the 4.10.0-11 and 4.10.0-13 kernels and with
systemd 232-18ubuntu1 and 232-19. I'm attaching the journal from one of
the test runs, taken from within the nspawn container while the test was
hung (using linux
10 matches
Mail list logo
