test_unconfined_userns from ubuntu_qrt_apparmor failed with J-oem-6.5

Bug #2036955 reported by Po-Hsu Lin
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
QA Regression Testing
In Progress
Undecided
Unassigned
ubuntu-kernel-tests
New
Undecided
Unassigned

Bug Description

Issue found with J-oem-6.5.0-1004.4

After checking with the test history of -1003, this appears to be a new test case added last week:
https://git.launchpad.net/qa-regression-testing/commit/?id=6f2c5ab7c8659174adac772ce0e894328bb5045d

Test failed with:
 Running test: './test-apparmor.py' distro: 'Ubuntu 22.04' kernel: '6.5.0-1004.4 (Ubuntu 6.5.0-1004.4-oem 6.5.3)' arch: 'amd64' init: 'systemd' uid: 0/0 SUDO_USER: 'ubuntu')
 Skipping private tests
 stderr:
 test_unconfined_userns (__main__.ApparmorTest)
 Test that unconfined userns restrictions are applied ... (disabling userns restrictions) (checking unshare works as normal) (enabling userns restrictions) (checking unshare fails) (creating unconfined mode profile for unshare with userns permission) FAIL

 ======================================================================
 FAIL: test_unconfined_userns (__main__.ApparmorTest)
 Test that unconfined userns restrictions are applied
 ----------------------------------------------------------------------
 Traceback (most recent call last):
   File "/home/ubuntu/autotest/client/tmp/ubuntu_qrt_apparmor/src/qa-regression-testing/scripts/./test-apparmor.py", line 1549, in test_unconfined_userns
     self.assertEqual(expected, rc, result + report)
 AssertionError: 0 != 1 : Got exit code 1, expected 0
 AppArmor parser error for /tmp/testlibh44rj8zq/unshare.profile in profile /tmp/testlibh44rj8zq/unshare.profile at line 1: syntax error, unexpected TOK_END_OF_RULE, expecting TOK_MODE

 ----------------------------------------------------------------------
 Ran 1 test in 1.290s

 FAILED (failures=1)

Related branches

Revision history for this message
Alex Murray (alexmurray) wrote :
Changed in qa-regression-testing:
status: New → In Progress
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.