action #154543
closed[qe-core] on s390x test fails in first_boot - display-manager not showing
0%
Description
Observation¶
openQA test in scenario sle-15-SP6-Full-s390x-skip_registration+workaround_modules@s390x-kvm fails in
first_boot
Test suite description¶
Testsuite maintained at https://gitlab.suse.de/qa-maintenance/qam-openqa-yml. Maintainer: slindomansilla
Like skip_registration test suite, but enable all modules as custom addons.
For internal testing, not simulating customer workflows
See https://progress.opensuse.org/issues/25264 for details. For now only "INSTALLONLY=1", later could be extended to do a full test run.
Reproducible¶
Fails since (at least) Build 46.40
Expected result¶
Last good: (unknown) (or more recent)
The gdm display-manager should show, enabling a user login.
Further details¶
Checking the systemctl logs show the display-manager as loaded, active and running.
Always latest result in this scenario: latest
Updated by openqa_review 2 months ago
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: allmodules+allpatterns-gnome
https://openqa.suse.de/tests/13492064#step/first_boot/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.