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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1848587
Title:
lxc 3.0.4-0ubuntu1 ADT test failure with linux 5.4.0-1.2
To manage
** Changed in: lxc (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1848587
Title:
lxc 3.0.4-0ubuntu1 ADT test failure with linux 5.4.0-1.2
To
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1848587
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
Bugs, which is subscribed to Ubuntu.
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
