I've thoroughly tested apparmor 2.10.95-0ubuntu2.2 in xenial-proposed. I've verified that this bug is fixed (via QRT's test-apparmor.py, as mentioned in Test Case in the description) and I've also went through the AppArmor Test Plan (excluding the Ubuntu Touch specific tests):
The Test Plan includes running the entire set of upstream AppArmor tests, a number of integration tests, libvirt tests, LXC/LXD tests, docker.io tests, Snappy confinement tests, etc.
I've thoroughly tested apparmor 2.10.95-0ubuntu2.2 in xenial-proposed. I've verified that this bug is fixed (via QRT's test-apparmor.py, as mentioned in Test Case in the description) and I've also went through the AppArmor Test Plan (excluding the Ubuntu Touch specific tests):
https:/ /wiki.ubuntu. com/Process/ Merges/ TestPlans/ AppArmor
The Test Plan includes running the entire set of upstream AppArmor tests, a number of integration tests, libvirt tests, LXC/LXD tests, docker.io tests, Snappy confinement tests, etc.