aims team mailing list archive

[Stefan Huehner <1504781@xxxxxxxxxxxxxxxxxx>]

Hello Stephane,

we have tested the propose 0.7.5-3ubuntu70  package in precise.

We have verified that with latest 3.2.0 kernel having the regression
(linux-image-3.2.0-93-generic) using the updated lxc package from
proposed fixes the bug and lxc-start works again correctly.

We have also verified that installing same 0.7.5-3ubuntu70  from
proposed with older kernel linux-headers-3.2.0-91 not having the
regression still works with the new lxc package.


Note:
In all cases we noticed another apparmor DENIED entry on lxc-shutdown (both old+new kernel) however it seems to not directly affect functionality and not be directly related to this bug (just for info here):
[2459430.608467] type=1400 audit(1446744853.293:20): apparmor="DENIED" operation="mount" info="failed flags match" error=-13 parent=5970 profile="lxc-container-default" name="/" pid=5979 comm="mount" flags="ro, remount"


** Tags removed: verification-needed
** Tags added: verification-done

-- 
You received this bug notification because you are a member of AIMS,
which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1504781

Title:
  lxc-test-ubuntu hangs forever in trusty-proposed with Linux 3.13.0-66:
  AppArmor denies /dev/ptmx mounting

Status in lxc source package in Precise:
  Fix Committed
Status in lxc source package in Trusty:
  Fix Released

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://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-trusty/trusty/amd64/l/lxc/20151010_103318@/log.gz
  https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-trusty/trusty/i386/l/lxc/20151010_103325@/log.gz

  https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-trusty/trusty/amd64/l/lxc/20151009_085841@/log.gz
  https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-trusty/trusty/i386/l/lxc/20151009_091723@/log.gz

  https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-trusty/trusty/amd64/l/lxc/20151010_105332@/log.gz
  https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-trusty/trusty/i386/l/lxc/20151010_114021@/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/precise/+source/lxc/+bug/1504781/+subscriptions