On Thu, Oct 10, 2013 at 10:12:39AM +0300, Timo Jyrinki wrote: > Hi, > > Thanks to the efforts yesterday, an lxc problem was identified and > fixed > (https://lists.ubuntu.com/archives/saucy-changes/2013-October/011959.html) > during the night my time. > > However, cyphermox reported to me that he updated the containers and > the 'check' (autopilot) jobs of cu2d continue to fail. So the dbus <-> > apparmor <-> lxc triangle is not yet in complete harmony. He suggested > checking the /var/log/upstart/lightdm.log and sending it to stgraber / > security team. So here goes: > > http://pastebin.ubuntu.com/6216936/ > > It's taken from dx-autopilot-intel and the latest container > saucy-i386-20131010-0216. > > -Timo > > ps. thanks Evan for the ubuntu-engineering post
Can you make sure the host is up to date, reboot it after that (since the dbus apparmor changes came through a kernel change) and then tell me what version of LXC is on the host and attach the "dmesg" output right after a failure. If it's really still an apparmor profile issue, there will be denials in the dmesg output, if not, then it's something else that's breaking your tests. Thanks -- Stéphane Graber Ubuntu developer http://www.canonical.com
signature.asc
Description: Digital signature
-- Mailing list: https://launchpad.net/~canonical-ci-engineering Post to : [email protected] Unsubscribe : https://launchpad.net/~canonical-ci-engineering More help : https://help.launchpad.net/ListHelp
