This bug was fixed in the package lxc - 3.0.3-0ubuntu1~18.04.3
---
lxc (3.0.3-0ubuntu1~18.04.3) bionic; urgency=medium
* Fix tests issue by avoiding falling back to inexistent trusty LXC images
and using the bionic ones (LP: #1939537)
lxc (3.0.3-0ubuntu1~18.04.2) bionic;
cross test of lxd fails, but i386 is not supported under ESM and i'm not
sure if i386 cross-arch autopkgtest is valid at all.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
autopkgteest & general usage of lxc 3.0.3-0ubuntu1~18.04.3 works with
host kernels on bionic's GA kernel and on hwe v5.4 kernels now.
verification done.
** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done verification-done-bionic
--
You received
** Description changed:
+ [ Impact ]
+
+ * Test suite fails due to inexistent device (/dev/network_latency).
+
+ [ Test Plan ]
+
+ * Run the test suite.
+ * The test should pass.
+
+ [ Where problems could occur ]
+
+ * The regression risk is very low, and the changes only affect the
+
Hello Seth, or anyone else affected,
Accepted lxc into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/lxc/3.0.3-0ubuntu1~18.04.3 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
it must be released in bionic-updates.
bionic-proposed is insufficient.
this follows the previous SRUs that fixed adt only, which were awaiting on "an
end-user visible sru to come in the future" which never has.
autopkgtest infrastructure has no ability to always test against proposed
pocket, a
Is bionic-proposed sufficient (ie. block-proposed-bionic then) or do you
specifically need it in bionic-updates?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1848587
Title:
This bug was fixed in the package lxc - 3.0.4-0ubuntu2
---
lxc (3.0.4-0ubuntu2) focal; urgency=medium
* Cherry-pick upstream bugfixes (LP: #1848587):
- tests: use /dev/loop-control instead of /dev/network_latency
-- Stéphane Graber Tue, 26 Nov 2019 12:22:37
-0500
**
Do you have an ETA on when you'll do an lxc upload with the fix?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1848587
Title:
lxc 3.0.4-0ubuntu1 ADT test failure with linux
** Changed in: lxc (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1848587
Title:
lxc 3.0.4-0ubuntu1 ADT test failure with
Sorry, mail got lost. Here's a fix:
https://github.com/lxc/lxc/pull/3187
** Changed in: lxc (Ubuntu)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
Christian: Discussed this bug with stgraber last week. Sounds like
/dev/network_latency is just an arbitrary device picked for a test case,
and since it's been removed upstream a different device should be used.
He said you could get this fixed.
** Changed in: lxc (Ubuntu)
Importance:
Seems /dev/network_latency was removed upstream.
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=c3082a674f46fe49383b157882c41dfabaa37113
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in
Looking at the linked reports, it sounds like either
/dev/network_latency doesn't exist in those systems (which would differ
from standard kernel behavior on Ubuntu), or there is a legitimate issue
with injecting that device afterwards.
In either case, likely to be a kernel config change or a
14 matches
Mail list logo
