qrt apparmor reports fatal error on Trusty ppc64le (3.13.0-107.154)

[Po-Hsu Lin]

A side-by-side diff for test result between 3.13.0-106.153 and 3.13.0-107.154 shows that there are some changes to the qrt apparmor test suite

The "syscall" test in test_regression_testsuite:
running syscall
FAIL: sysctl read failed - Function not implemented
 Fatal Error (syscall_sysctl): Unexpected shell error. Run with -x to debug
 Fatal Error (syscall_mknod): Unexpected shell error. Run with -x to debug

These Fatal Errors are new, but perhaps these are expected.
I think the root cause is still the sysctl is not implemented issue. And these two lines will make people (at least me) think if there are some other regressions occurred.

Especially the syscall_mknod, as the FAIL message only states that sysctl read error, didn't mention mknod here.

[Sean Feole (sfeole)]

 very old bug, with no action on it, qrt_apparmor appears to be passing on ppc64 / latest sru cycle, marking bug as incomplete and will close in 5 days if no update.

[Po-Hsu Lin (cypressyew)]

We don't have a test report for the most recent SRU cycle (node broken)

But from the test result for kernel 3.13.0-153.203, this test looks good.

http://10.246.72.4/test-results/3.13.0-153.203-generic/entei__3.13.0-153.203__2018-06-20_16-34-00/ubuntu_qrt_apparmor/results/ubuntu_qrt_apparmor.test-apparmor.py/debug/ubuntu_qrt_apparmor.test-apparmor.py.DEBUG.html

I will mark this one as fix-released.
Thanks