action #23834
closed[sle][functional][s390x][zkvm]test fails as incomplete in reconnect_s390 with "error: The domain is not running" -> should turn into fail
0%
Description
Observation¶
openQA test in scenario sle-15-Leanos-DVD-s390x-create_hdd_minimal_base+sdk@zkvm fails in
with "error: The domain is not running"
in
https://openqa.suse.de/tests/1140536/file/serial0.txt
with output in autoinst-log.txt:
19:22:54.0936 3683 Connection to root@s390pb.suse.de established
error: The domain is not running
19:22:54.4756 3681 ||| finished redefine_svirt_domain installation at 2017-08-31 19:22:54 (3 s)
19:22:54.4760 3681 ||| starting reconnect_s390 tests/installation/reconnect_s390.pm at 2017-08-31 19:22:54
19:22:54.4765 Debug: /var/lib/openqa/cache/tests/sle/tests/installation/reconnect_s390.pm:44 called testapi::wait_serial
19:22:54.4767 3681 <<< testapi::wait_serial(timeout=300, regexp=qr/(?^:Welcome to SUSE Linux Enterprise Server.*\(s390x\))/)
19:22:55.7109 3683 considering VNC stalled, no update for 4.04 seconds
DIE socket does not exist. Probably your backend instance could not start or died. at /usr/lib/os-autoinst/consoles/VNC.pm line 881.
Reproducible¶
Fails since (at least) Build 173.4
Expected result¶
Job should fail and not incomplete.
Suggestion¶
Can we better catch what's happening on the hypervisor host and detect that the SUT does not run and catch that?
Further details¶
Always latest result in this scenario: latest
Updated by okurz over 6 years ago
- Assignee deleted (
okurz)
I wanted to take a look into this with mgriessmeier today but did not remember to bring it up. Unassigning before my absence.
Updated by mgriessmeier over 6 years ago
I hoped this to be fixed by https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/3552
but unfortunately is not
Updated by okurz over 6 years ago
- Related to action #25584: [sle][functional][s390x][sporadic][medium] backend connection lost during "partitioning_warnings", vnc stalled, etc -> should turn into fail added
Updated by okurz over 6 years ago
- Due date set to 2018-01-30
- Assignee set to mgriessmeier
- Target version changed from Milestone 12 to Milestone 13
please check shortly if we do have this covered already by the recent changes. If not then please move to next sprint (and optionally unassign)
Updated by mgriessmeier over 6 years ago
- Status changed from In Progress to Resolved
this should've been covered - didn't see any related error
"The domain is not running" was never the actual problem here