lxc-test-ubuntu hangs forever in trusty-proposed with Linux 3.13.0-66: AppArmor denies /dev/ptmx mounting
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
lxc (Ubuntu) | ||||||
Precise |
Fix Released
|
High
|
Unassigned | |||
Trusty |
Fix Released
|
High
|
Unassigned |
Bug Description
=======
SRU Justification (for precise):
Impact: containers fail to start!
Regression potential: we only add a copy of an existing apparmor allow rule
with a different syntax (no trailing /), leaving the old one for older
aa/kernel. There should be no regressions.
Test case: lxc-create -t ubuntu -n u1; lxc-start -n u1
=======
We are seeing test suite failures under ADT testing with linux, linux-lts-utopic and linux-lts-vivid kernels:
https:/
https:/
https:/
https:/
https:/
https:/
description: | updated |
Changed in lxc (Ubuntu Precise): | |
importance: | Undecided → High |
Changed in linux (Ubuntu Precise): | |
importance: | Undecided → High |
description: | updated |
no longer affects: | linux (Ubuntu Trusty) |
no longer affects: | linux (Ubuntu Precise) |
no longer affects: | linux (Ubuntu) |
no longer affects: | lxc (Ubuntu) |
Changed in lxc (Ubuntu Trusty): | |
importance: | Undecided → High |
They all get stuck in lxc-test-ubuntu which would indicate either a hang in debootstrap (newly introduced debconf question) or a failure to reach the cloud image server.
In either case, you've not actually regressed LXC, the other tests would have failed if that was the case.
So I'd toss this one over to pitti for investigation and release the updated kernels regardless.