recent snapd path renames causes apparmor to not load profiles on boot

Bug #1569573 reported by Jamie Strandboge on 2016-04-12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
apparmor (Ubuntu)
Tyler Hicks

Bug Description

/lib/apparmor/functions has this:

The recent snappy path renames move the profiles to /var/lib/snapd/apparmor/profiles so now snappy apparmor profiles are not loading on boot.

apparmor needs this change:

Changed in apparmor (Ubuntu):
status: New → Triaged
importance: Undecided → Critical
assignee: nobody → Tyler Hicks (tyhicks)
Changed in apparmor (Ubuntu):
status: Triaged → In Progress
Changed in apparmor (Ubuntu):
status: In Progress → Fix Committed
Changed in snappy:
status: New → Fix Committed
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package apparmor - 2.10.95-0ubuntu2

apparmor (2.10.95-0ubuntu2) xenial; urgency=medium

  * debian/patches/r3435-allow-dnsmasq-access-to-lxd-bridge.patch: Grant
    access to the new default bridge configuration in LXD 2.0.0 (LP: #1566944)
  * debian/patches/r3437-add-attach-disconnected-to-dnsmasq.patch: Add the
    attach_disconnected flag to the dnsmasq profile in order to prevent a
    disconnected path denial triggered by the latest network-manager upload
    (LP: #1569316)
  * debian/lib/apparmor/functions: Reference the new path used for snapd
    AppArmor profiles to fix a bug which left those profiles unloaded after
    booting (LP: #1569573)

 -- Tyler Hicks <email address hidden> Tue, 12 Apr 2016 16:59:46 -0500

Changed in apparmor (Ubuntu):
status: Fix Committed → Fix Released
Leo Arias (elopio) wrote :
Changed in snappy:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers