recent snapd path renames causes apparmor to not load profiles on boot
Bug #1569573 reported by
Jamie Strandboge
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Snappy |
Fix Released
|
Undecided
|
Unassigned | ||
apparmor (Ubuntu) |
Fix Released
|
Critical
|
Tyler Hicks |
Bug Description
/lib/apparmor/
PROFILES_
The recent snappy path renames move the profiles to /var/lib/
apparmor needs this change:
PROFILES_
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 |
Changed in snappy: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
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 patches/ r3437-add- attach- disconnected- to-dnsmasq. patch: Add the disconnected flag to the dnsmasq profile in order to prevent a lib/apparmor/ functions: Reference the new path used for snapd
access to the new default bridge configuration in LXD 2.0.0 (LP: #1566944)
* debian/
attach_
disconnected path denial triggered by the latest network-manager upload
(LP: #1569316)
* debian/
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