action #99039
closed
[qe-core] test fails in pam
Added by dimstar about 3 years ago.
Updated almost 3 years ago.
Category:
Bugs in existing tests
Description
Observation¶
openQA test in scenario opensuse-Tumbleweed-DVD-x86_64-extra_tests_textmode@64bit fails in
pam
the subpackage pam-deprecated is now gone for good, the new pam version no longer brings the tally2 and cracklib pam modules, not even optionally.
Test suite description¶
Maintainer: slindomansilla@suse.de.
Mainly post-installation console extra tests.
Reproducible¶
Fails since (at least) Build 20210909
Expected result¶
Last good: 20210908 (or more recent)
Further details¶
Always latest result in this scenario: latest
- Has duplicate action #99036: test fails in pam: Test relies on pam-deprecated, which got dropped added
- Subject changed from test fails in pam to [qe-core] test fails in pam
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: extra_tests_textmode
https://openqa.opensuse.org/tests/1955495
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
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: extra_tests_textmode
https://openqa.opensuse.org/tests/1981633
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
- Priority changed from Normal to High
Bumping prio - we still have pam failing - pam being one of the most essential stacks we can possibly have.
so far we fly blind here (the pam-deprecated non-existance is clear - but failing for +1 month on that risks to hide more bugs in pam tests)
- Status changed from New to In Progress
- Assignee set to punkioudi
I propose as a first step the following [PR], where the tests of the two deprecated pam modules are being removed.
I think though that it would be nice to implement two similar tests with the modules that have replaced them : pam_faillock and pam_passwdqc. It can be handled as a separate progress ticket, @tjyrinki_suse wdyt?
- Status changed from In Progress to Resolved
- % Done changed from 0 to 100
- Target version set to QE-Core: Ready
Also available in: Atom
PDF