action #36268
closed[sle][functional][u][hard][s390x] test fails in consoletest_finish - screen does not show desktop session
0%
Description
Observation¶
openQA test in scenario sle-12-SP4-Server-DVD-s390x-allpatterns@zkvm fails in
consoletest_finish
not showing the desktop screen which we would expect there
Acceptance criteria¶
- AC1: Test suite works or fails on confirmed bug
Suggestions¶
On the video we can see that gnome session is there for second or two, but then it's black screen. So it can be that lock screen is broken, gnome crashes or there is an issue with setup.
Requires investigation.
Reproducible¶
Fails since (at least) Build 0234
Expected result¶
Last good: 0233 (or more recent)
Problem¶
Seems to be reproducible since recently. Did we introduce a regression?
Further details¶
Always latest result in this scenario: latest
Updated by okurz almost 6 years ago
- Subject changed from [sle][functional][u] test fails in consoletest_finish - needle match issue to [sle][functional][u][fast] test fails in consoletest_finish - screen does not show desktop session
- Description updated (diff)
- Due date set to 2018-05-22
- Priority changed from Normal to High
- Target version set to Milestone 16
@zluo you can value test failures that are clearly reproducible as "high" at least by default.
Updated by mgriessmeier almost 6 years ago
- Due date changed from 2018-05-22 to 2018-06-05
Updated by riafarov almost 6 years ago
- Subject changed from [sle][functional][u][fast] test fails in consoletest_finish - screen does not show desktop session to [sle][functional][u] test fails in consoletest_finish - screen does not show desktop session
- Description updated (diff)
- Status changed from New to Workable
Updated by SLindoMansilla almost 6 years ago
- Subject changed from [sle][functional][u] test fails in consoletest_finish - screen does not show desktop session to [sle][functional][u][hard] test fails in consoletest_finish - screen does not show desktop session
Updated by oorlov almost 6 years ago
- Related to action #34837: [sle12][functional][u][s390x-kvm] test fails in consoletest_finish while switching from console to GUI desktop, stuck on black screen added
Updated by oorlov almost 6 years ago
- Blocked by action #34003: [tools] Better logging and error handling in case of remote console connections in consoles or backends, e.g. ssh added
Updated by oorlov almost 6 years ago
- Related to deleted (action #34837: [sle12][functional][u][s390x-kvm] test fails in consoletest_finish while switching from console to GUI desktop, stuck on black screen)
Updated by oorlov almost 6 years ago
- Has duplicate action #34837: [sle12][functional][u][s390x-kvm] test fails in consoletest_finish while switching from console to GUI desktop, stuck on black screen added
Updated by okurz almost 6 years ago
- Has duplicate deleted (action #34837: [sle12][functional][u][s390x-kvm] test fails in consoletest_finish while switching from console to GUI desktop, stuck on black screen)
Updated by okurz almost 6 years ago
- Has duplicate action #34837: [sle12][functional][u][s390x-kvm] test fails in consoletest_finish while switching from console to GUI desktop, stuck on black screen added
Updated by mgriessmeier almost 6 years ago
- Due date changed from 2018-06-05 to 2018-06-19
seems to be still blocked, moving
Updated by okurz almost 6 years ago
- Due date changed from 2018-06-19 to 2018-07-31
- Target version changed from Milestone 16 to Milestone 18
needs #34003 first
Updated by mloviska almost 6 years ago
- Status changed from Blocked to Workable
https://progress.opensuse.org/issues/34003 has been resolved. Unblocking this one.
Updated by okurz almost 6 years ago
- Target version changed from Milestone 18 to Milestone 18
Updated by nicksinger almost 6 years ago
For some reason we run "test -d /home/*/.local/share/xorg" in the test which returns 1 and therefore fails. Maybe this also explains why we can't see any X running? We just need to figure out why this check was added (didn't find it after a quick look).
Updated by okurz almost 6 years ago
- Subject changed from [sle][functional][u][hard] test fails in consoletest_finish - screen does not show desktop session to [sle][functional][u][hard][s390x] test fails in consoletest_finish - screen does not show desktop session
Where did you see this? I doubt this is related. I can see some s390x tests that reach an X-session, e.g. https://openqa.suse.de/tests/1783986#step/consoletest_setup/1 so it can work in general.
Updated by mgriessmeier almost 6 years ago
fwiw:
in the video we see for one frame that there is a X server running with gnome
https://openqa.suse.de/tests/1783980/file/video.ogv (watch it with mpv)
Updated by mgriessmeier almost 6 years ago
to check statistics, triggered 100 jobs over the weekend:
https://openqa.suse.de/tests/overview?build=0273%3As390x_poo36268&distri=sle&groupid=132&version=12-SP4
H1: journalctl shows that dhcp lease was released in yast2_lan, so could be that the re-request sometimes takes so long that the vnc connection is silently disconnected
H2: gdm crashed
Updated by mgriessmeier almost 6 years ago
100 triggered jobs over the weekend showed following results:
- 76 fails in consoletest_finish
- 22 passed this stage and failed in reboot_gnome
- 1 incomplete
- 1 fail in installation_overview
Updated by mgriessmeier almost 6 years ago
- Status changed from Workable to In Progress
- Assignee set to mgriessmeier
so we have 3 out of 4 fails, to crosscheck we have triggered 4 jobs with SP3 and 4 jobs with excluding the intermediate modules:
https://openqa.suse.de/tests/overview?groupid=132&build=0273%3As390x_poo36268&distri=sle
Updated by okurz almost 6 years ago
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: system_performance
https://openqa.suse.de/tests/1825234
Updated by oorlov almost 6 years ago
- Blocks action #36279: [sle][functional][u][s390x][medium] test fails in reboot_gnome on bsc#1085181 - help with investigation using new shutdown debug method added
Updated by mgriessmeier almost 6 years ago
- Description updated (diff)
updated latest link to match s390x-kvm-sle12 machine
Updated by okurz almost 6 years ago
- Blocks action #34402: [functional][u][s390x][medium] Revisit extra_tests_on_gnome@s390x (was: Do no run extra_tests_on_gnome on s390x) added
Updated by mgriessmeier over 5 years ago
I'm out of ideas...
the only thing which I could try as workaround is to retry the switch to the x11 console...
Updated by okurz over 5 years ago
- Assignee deleted (
mgriessmeier)
I think we agreed that you do not want to work on this and therefore should be unassigned, right?
Updated by mgriessmeier over 5 years ago
- Due date changed from 2018-07-31 to 2018-08-14
- Status changed from In Progress to Workable
Updated by okurz over 5 years ago
- Due date changed from 2018-08-14 to 2018-08-28
bulk move to next sprint as could not be discussed in SR
Updated by mgriessmeier over 5 years ago
- Due date changed from 2018-08-28 to 2018-09-11
Updated by oorlov over 5 years ago
- Status changed from Workable to Feedback
Fixed by PR: https://gitlab.suse.de/openqa/os-autoinst-needles-sles/merge_requests/921.
The issue was because of blank screen appearing. New needle allows to call 'ensure_unlocked_desktop' which allows to go out from the screen lock.
Updated by mgriessmeier over 5 years ago
oorlov wrote:
Fixed by PR: https://gitlab.suse.de/openqa/os-autoinst-needles-sles/merge_requests/921.
The issue was because of blank screen appearing. New needle allows to call 'ensure_unlocked_desktop' which allows to go out from the screen lock.
at least in Build 0374 I cannot see any failing jobs on s390x in consoletest_finish. nevertheless, since it's sporadic, let's wait for one more build to get more statistics
great job anyway!
Updated by mgriessmeier over 5 years ago
- Status changed from Feedback to Resolved
no fails regarding that in the recent two builds - let's resolve for now