test_regression_mqueue_abi from ubuntu_qrt_apparmor is failing with F-5.15 ARM64

Bug #2051227 reported by Po-Hsu Lin
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
QA Regression Testing
Fix Released
Undecided
Unassigned
ubuntu-kernel-tests
Fix Released
Undecided
Unassigned

Bug Description

Issue found on:
 * F-azure-5.15.0-1055.63~20.04.1 ARM64 Standard_D2pds_v5
 * F-aws-5.15.0-1053.58~20.04.1 ARM64 c6g.8xlarge
 * F-lowlatency-hwe-5.15.0-94.104~20.04.1 64k ARM64 openstack
 * F-hwe-5.15.0-94.104~20.04.1 64k ARM64 openstack

(We don't run this test on baremetal with F-hwe-5.15 / F-lowlatency-hwe-5.15)

This issue cannot be found on J-5.15.

Test failed with:
 Running 'python2 ./test-apparmor.py -v ApparmorTestsuites.test_regression_mqueue_abi'
 Running test: './test-apparmor.py' distro: 'Ubuntu 20.04' kernel: '5.15.0-1053.58~20.04.1 (Ubuntu 5.15.0-1053.58~20.04.1-aws 5.15.136)' arch: 'arm64' init: 'systemd' uid: 0/0 SUDO_USER: 'ubuntu')
 test_regression_mqueue_abi (__main__.ApparmorTestsuites)
 Skipping private tests

 Test if abi is working properly ... (Applying patch 0001-tests-regression-apparmor-syscall.sh-fail-iopl-ioper.patch) (Applying patch 0001-tests-regression-apparmor-capabilities.sh-fail-iopl-.patch) (Applying patch use-pyflakes3-with-2.13.patch) (Applying patch 0001-regression-tests-add-FIPS-140-2-lib-validation-hmac-.patch) FAIL

 ======================================================================
   preparing apparmor_2.13.3-7ubuntu5.3.dsc... done
 FAIL: test_regression_mqueue_abi (__main__.ApparmorTestsuites)
 Test if abi is working properly
 ----------------------------------------------------------------------
 Traceback (most recent call last):
   File "./test-apparmor.py", line 2055, in test_regression_mqueue_abi
     self.assertEqual(expected, rc, result + report)
 AssertionError: Got exit code 1, expected 0
 Unrecognized option

 Usage: /tmp/testlib4X340M/source/focal/apparmor-2.13.3/tests/regression/apparmor/posix_mq_rcv [options]
 Options are:
 -n get notified if there's an item in the queue
           available options are: mq_notify, select, poll and epoll
 -k message queue name (default is /testmq)
 -c path of the client binary
 -u run test as specified UID
 -t timeout in seconds

 ----------------------------------------------------------------------
 Ran 1 test in 20.176s

 FAILED (failures=1)

The failing command is this line in test-apparmor.py:
  rc, report = testlib.cmd([posix_mq_rcv, '-c', posix_mq_snd])

It's trying to run:
  $path_to_apparmor_source/apparmor-2.13.3/tests/regression/apparmor/posix_mq_rcv -c $path_to_apparmor_source/apparmor-2.13.3/tests/regression/apparmor/posix_mq_snd

However it does not recognize the -c flag, despite it's printing out option for that flag.

I can't reproduce this issue with 5.15.0-1053.61~20.04.1 on Standard_D2pds_v5

Po-Hsu Lin (cypressyew)
summary: - test_regression_mqueue_abi from ubuntu_qrt_apparmor is failing with 5.15
- ARM64
+ test_regression_mqueue_abi from ubuntu_qrt_apparmor is failing with
+ F-5.15 ARM64
description: updated
Po-Hsu Lin (cypressyew)
description: updated
Revision history for this message
Po-Hsu Lin (cypressyew) wrote :

This is affecting the posix_ipc test in test_regression_testsuite as well, it's failing with the same -c flag issue:

+ /tmp/testlibQZ3lGV/source/focal/apparmor-2.13.3/tests/regression/apparmor/posix_mq_rcv /tmp/testlibQZ3lGV/source/focal/apparmor-2.13.3/tests/regression/apparmor/posix_mq_snd pass -c /tmp/testlibQZ3lGV/source/focal/apparmor-2.13.3/tests/regression/apparmor/posix_mq_snd -k /queuename
+ test_rc=1
+ '[' 1 -gt 128 ']'
+ checktestfg
+ local ret expectedsig killedsig
++ cat /tmp/sdtest.29193-28058-rxK9s7/output.posix_mq_rcv
+ ret='Unrecognized option

Usage: /tmp/testlibQZ3lGV/source/focal/apparmor-2.13.3/tests/regression/apparmor/posix_mq_rcv [options]
Options are:
-n get notified if there'\''s an item in the queue
          available options are: mq_notify, select, poll and epoll
-k message queue name (default is /testmq)
-c path of the client binary
-u run test as specified UID
-t timeout in seconds'

Revision history for this message
Georgia Garcia (georgiag) wrote :
Revision history for this message
Po-Hsu Lin (cypressyew) wrote :

Thanks for the quick fix Garcia!

I have tests restarted and this getopt issue does not exist anymore.

Changed in qa-regression-testing:
status: New → Fix Released
Changed in ubuntu-kernel-tests:
status: New → Fix Released
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.