action #63211
closed
[sle][security][sle15sp2] test fails in first_boot due to the boot sequence is not progressing after soft-fail.
Added by bchou about 4 years ago.
Updated about 4 years ago.
Category:
Bugs in existing tests
Description
Observation¶
openQA test in scenario sle-15-SP2-Online-x86_64-fips_ker_mode_tests_crypt_install@64bit fails in
first_boot
Test suite description¶
Reproducible¶
Fails since (at least) Build 136.1
Expected result¶
Last good: 134.1 (or more recent)
Further details¶
Always latest result in this scenario: latest
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: fips_ker_mode_tests_crypt_install
https://openqa.suse.de/tests/3908301
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
- Status changed from In Progress to Blocked
The poo was causes by the 2 bugs as
Bug 1086425 - tracker bug for bgo#657996: user selection in gdm for relogin: First / only user account not selected by default; have to use mouse to login
Bug 1164856 - tracker bug for bgo#657996: user selection in gdm for relogin: First / only user account not selected by default; have to use mouse to login
There is nothing to do for the poo so far.
- Status changed from Blocked to Closed
Also available in: Atom
PDF