Unfortunately, the AppArmor kernel patches that were included in the 4.4.0-15.31 made a slight behavioral change that affects the failing testcases, returning a different error value. As part of landing the user space patches upstream, these have been adjusted in the upstream tests in http://bazaar.launchpad.net/~apparmor-dev/apparmor/master/revision/3401 and are expected to land in xenial in the next few days.
The kernel does not need to block on these two failures.
Unfortunately, the AppArmor kernel patches that were included in the 4.4.0-15.31 made a slight behavioral change that affects the failing testcases, returning a different error value. As part of landing the user space patches upstream, these have been adjusted in the upstream tests in http:// bazaar. launchpad. net/~apparmor- dev/apparmor/ master/ revision/ 3401 and are expected to land in xenial in the next few days.
The kernel does not need to block on these two failures.
Thanks!