action #168445
openaction #166613: Yast default selected LSM changes from Apparmor to SELinux, existing openQA test fails in first_boot
[security][tumbleweed] audit 4: test fails in ausearch and aulastlog
0%
Description
Observation¶
"ausearch -i --arch x86_64" does not list any results.
The reason might be due to autrace before failing (autrace no longer exists) and the ausearch test relying on log entries filed by "the autrace test module"; dropping autrace from the schedule does not fix ausearch 'just like that' (so not rolling back to the lastgood snapshot does not help it)
openQA test in scenario opensuse-Tumbleweed-DVD-x86_64-security_audit@64bit fails in
ausearch
Test suite description¶
Reproducible¶
Fails since (at least) Build 20240930
Expected result¶
Last good: 20240929 (or more recent)
Further details¶
Always latest result in this scenario: latest
Updated by szarate about 1 month ago
- Parent task set to #166613
Contact @cahu if any questions.
cc @tjyrinki_suse
Looks like for apparmor and security audit testsuites need to be reworked too. #168571 can be rejected in favor of #167662
Updated by szarate about 1 month ago
- Subject changed from audit 4: test fails in ausearch and aulastlog to [qe-security] audit 4: test fails in ausearch and aulastlog
Updated by tjyrinki_suse 22 days ago
- Subject changed from [qe-security] audit 4: test fails in ausearch and aulastlog to [security] audit 4: test fails in ausearch and aulastlog
- Status changed from New to Workable
- Start date deleted (
2024-10-18)
Updated by tjyrinki_suse 22 days ago
- Subject changed from [security] audit 4: test fails in ausearch and aulastlog to [security][tumbleweed] audit 4: test fails in ausearch and aulastlog
Updated by tjyrinki_suse 22 days ago
- Related to action #167662: [security][tumbleweed] test fails in aa_enforce: audit 4.0 changes need adaption added
Updated by FSzekely 20 days ago
- Status changed from Workable to In Progress
- Assignee set to FSzekely
ausearch -i --arch x86_64 does not list results because there is no audit rule which would produce log line(s) including "arch=...".
The fix for this is easy, as I did pretty much the same for
https://progress.opensuse.org/issues/169060.
Updated by openqa_review 6 days ago
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: security_audit
https://openqa.opensuse.org/tests/4647245#step/aulastlog/1
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" or "EOL" (End-of-Life)
- The bugref in the openQA scenario is removed or replaced, e.g.
label:wontfix:boo1234
Expect the next reminder at the earliest in 28 days if nothing changes in this ticket.