[Bug 978297] Re: apparmor should quietly return success in a container

[Jamie Strandboge]

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
Foundations Bugs, which is subscribed to upstart in Ubuntu.
https://bugs.launchpad.net/bugs/978297

Title:
  apparmor should quietly return success in a container

Status in “apparmor” package in Ubuntu:
  In Progress
Status in “upstart” package in Ubuntu:
  Fix Committed
Status in “apparmor” source package in Precise:
  In Progress
Status in “upstart” source package in Precise:
  Fix Committed

Bug description:
  In precise, containers are not allowed to load profiles.  This will be
  allowed later, but for now apparmor should not prevent things from
  starting in a container because of failures to load or transition to
  profiles.

  1. /etc/init.d/apparmor should return 0 if in a container

  2. /lib/init/apparmor-profile-load should do nothing and return 0 if
  in a container.

  Since the container is already locked into a (customizable) container
  profile, this is ok.

  (Note that admins can have containers running unconfined and with all
  capabilities, but that is a special case.)

  THis is needed for bug 978147.

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