ubuntu_qrt_apparmor: proto:icmp, type:dgram, domain:inet failures

[Andrea Righi]

[Impact]

We are getting the following error with the latest lunar kernel (6.2.0-20.20) on amd64, arm64 and ppc64el:

19:41:52 ERROR| [stderr] test_protocol (__main__.ApparmorNetwork.test_protocol)
19:41:52 ERROR| [stderr] Test network protocol ... FAIL
19:41:52 ERROR| [stderr]
19:41:52 ERROR| [stderr] ======================================================================
19:41:52 ERROR| [stderr] FAIL: test_protocol (__main__.ApparmorNetwork.test_protocol)
19:41:52 ERROR| [stderr] Test network protocol
19:41:52 ERROR| [stderr] ----------------------------------------------------------------------
19:41:52 DEBUG| [stdout] Skipping private tests
19:41:52 DEBUG| [stdout]
19:41:52 DEBUG| [stdout] proto:icmp
19:41:52 ERROR| [stderr] Traceback (most recent call last):
19:41:52 ERROR| [stderr] File "/home/ubuntu/autotest/client/tmp/ubuntu_qrt_apparmor/src/qa-regression-testing/scripts/./test-apparmor.py", line 2898, in test_protocol
19:41:52 ERROR| [stderr] self.assertEqual(expected, rc, result + report)
19:41:52 ERROR| [stderr] AssertionError: 0 != 127 : Got exit code 127, expected 0 (icmp)
19:41:52 ERROR| [stderr] [Errno 2] No such file or directory: '/tmp/testlibys_4iax9/test-net.py'
19:41:52 ERROR| [stderr]

A similar error happens also with type:dgram and domain:inet.

The kernel doesn't seem to miss any apparmor-related patches, so it might be a user-space / test regression.

[John Johansen (jjohansen)]

This seems to be caused by test-net.py and test-unix-domain-connect.py explicitly using

  #!/usr/bin/python2

when I change this locally to

  #!/usr/bin/python3

the tests pass. This is a larger issue in qrt as there are still several tests beyond the subtes subtests for test-apparmor.py that are hard coding /usr/bin/python2. We will start working on a fix

[Andrea Righi (arighi)]

These errors are all caused by the fact that python2 has been removed in Lunar. It's a test issue, not apparmor-related.