Ah, after digging in to this, it was addressed in the upstream apparmor tree in http://bazaar.launchpad.net/~apparmor-dev/apparmor/master/revision/3446 (basically, stderr was not being captured correctly when attempting to check whether the sysctl() syscall was supported in the test environment). Interestingly, the patch had already been cherry-picked into QRT for the 14.04-backport of 16.04's apparmor (where ppc64el doesn't support the sysctl() syscall), but was not also applied when testing apparmor on 16.04.
Ah, after digging in to this, it was addressed in the upstream apparmor tree in http:// bazaar. launchpad. net/~apparmor- dev/apparmor/ master/ revision/ 3446 (basically, stderr was not being captured correctly when attempting to check whether the sysctl() syscall was supported in the test environment). Interestingly, the patch had already been cherry-picked into QRT for the 14.04-backport of 16.04's apparmor (where ppc64el doesn't support the sysctl() syscall), but was not also applied when testing apparmor on 16.04.
In any event, I have now modified the QRT test-apparmor.py script to apply the r3446 patch on 16.04 as well, in QRT git commit https:/ /git.launchpad. net/qa- regression- testing/ commit/ ?id=2646ed6f4e2 c8f9b38eb3210f9 3a7439c6e8e5f0
Thanks!