action #93405
closed
[Tumbleweed][security] test fails in audit2allow: no failure of getty_t reported (which is good)
Added by dimstar almost 3 years ago.
Updated almost 3 years ago.
Category:
Bugs in existing tests
Description
Observation¶
openQA test in scenario opensuse-Tumbleweed-DVD-x86_64-selinux@64bit fails in
audit2allow
AS the test comments indicate, the output can change at any time. Gut requested output format though seems too restrictive for the current Tumbleweed snapshot.
Test suite description¶
Maintainer (Lily Zhao) llzhao@suse.com
Reproducible¶
Fails since (at least) Build 20210601
Expected result¶
Last good: 20210527 (or more recent)
Further details¶
Always latest result in this scenario: latest
- Subject changed from test fails in audit2allow: no failure of getty_t reported (which is good) to [security] test fails in audit2allow: no failure of getty_t reported (which is good)
- Subject changed from [security] test fails in audit2allow: no failure of getty_t reported (which is good) to [Tumbleweed][security] test fails in audit2allow: no failure of getty_t reported (which is good)
- Assignee set to llzhao
- Estimated time set to 8.00 h
Thanks for filing this poo. I will fix it later.
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: selinux
https://openqa.opensuse.org/tests/1810997
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 label in the openQA scenario is removed
- Status changed from New to In Progress
- Assignee changed from llzhao to favogt
- Status changed from In Progress to Resolved
- % Done changed from 0 to 100
Also available in: Atom
PDF