Ok, tested this and compared the output of 'aa-status' before and after
a reboot. All the profiles are loaded on reboot with the new upstart.
Verified that /lib/init/apparmor-profile-load was updated on upgrade.
Comparing build logs between 1.5-0ubuntu3 and 1.5-0ubuntu4 (ie, this
patch) shows no surprises. Comparing binaries between the same two
versions show no surprises either.

I did not test this in containers, but Serge did before giving me the
patch and the logic in the script is obvious.

Uploaded to unapproved.

** Changed in: upstart (Ubuntu Precise)
       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/978297

Title:
  apparmor should quietly return success in a container

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/978297/+subscriptions

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to