action #77095
closed
[qe-core][opensuse]apparmor 3: aa_notify -l is no longer silent
Added by dimstar over 3 years ago.
Updated over 3 years ago.
Category:
Bugs in existing tests
Description
Observation¶
openQA test in scenario opensuse-Tumbleweed-DVD-x86_64-apparmor@64bit fails in
aa_notify
earlier versions of apparmor made no output if audit.log was empty when aa-notify-l was started. With apparmor 3.0, this has changed and the output is something along the lines of:
AppArmor denials: 0 (since Sat Nov 7 00:15:58 2020)
The test needs to catch up with this new reality
Test suite description¶
Maintainer: wnereiz.
Test AppArmor tool with an existing disk image.
Reproducible¶
Fails since (at least) Build 20201105 (current job)
Expected result¶
Last good: 20201104 (or more recent)
Further details¶
Always latest result in this scenario: latest
FYI: The behaviour/output changed with AppArmor 3.0 which includes a fully rewritten aa-notify (perl -> python).
The plan for Leap 15.x is to stay with AppArmor 2.13.x, so the changed behaviour is only in Tumbleweed.
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: apparmor
https://openqa.opensuse.org/tests/1478917
To prevent further reminder comments one of the following options should be followed:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released"
- The label in the openQA scenario is removed
- Subject changed from apparmor 3: aa_notify -l is no longer silent to [qe-core][opensuse]apparmor 3: aa_notify -l is no longer silent
- Start date deleted (
2020-11-06)
- Status changed from New to Workable
- Status changed from Workable to New
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: apparmor
https://openqa.opensuse.org/tests/1502598
To prevent further reminder comments one of the following options should be followed:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released"
- The label in the openQA scenario is removed
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: apparmor
https://openqa.opensuse.org/tests/1527523
To prevent further reminder comments one of the following options should be followed:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released"
- The label in the openQA scenario is removed
- Status changed from New to In Progress
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: apparmor
https://openqa.opensuse.org/tests/1593121
To prevent further reminder comments one of the following options should be followed:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released"
- The label in the openQA scenario is removed
- Status changed from In Progress to Resolved
Also available in: Atom
PDF