Project

General

Profile

Actions

action #48260

closed

[sle][functional][u][s390x][kvm] test fails in reboot_after_installation - "The console isn't responding correctly. Maybe half-open socket?"

Added by okurz about 5 years ago. Updated over 3 years ago.

Status:
Resolved
Priority:
Urgent
Assignee:
Category:
Bugs in existing tests
Target version:
SUSE QA - Milestone 23
Start date:
2019-02-21
Due date:
% Done:

0%

Estimated time:
Difficulty:

Description

Observation

openQA test in scenario sle-15-SP1-Installer-DVD-s390x-gnome@s390x-kvm-sle12 fails in
reboot_after_installation

autoinst-log.txt states:

[2019-02-21T23:50:25.512 CET] [debug] /var/lib/openqa/cache/openqa.suse.de/tests/sle/tests/installation/reboot_after_installation.pm:28 called power_action_utils::power_action
[2019-02-21T23:50:25.513 CET] [debug] <<< testapi::check_shutdown(timeout=180)
[2019-02-21T23:50:25.608 CET] [debug] Connection to root@s390p8.suse.de established
[2019-02-21T23:50:25.687 CET] [debug] Command executed: ! virsh  dominfo openQA-SUT-4 | grep -w 'shut off', ret=0
[2019-02-21T23:50:26.778 CET] [debug] Connection to root@s390p8.suse.de established
[2019-02-21T23:50:26.857 CET] [debug] Command executed: ! virsh  dominfo openQA-SUT-4 | grep -w 'shut off', ret=0
%@[2019-02-21T23:50:27.947 CET] [debug] Connection to root@s390p8.suse.de established
[2019-02-21T23:50:28.027 CET] [debug] Command executed: ! virsh  dominfo openQA-SUT-4 | grep -w 'shut off', ret=0

[2019-02-21T23:54:15.127 CET] [debug] Backend process died, backend errors are reported below in the following lines:
The console isn't responding correctly. Maybe half-open socket? at /usr/lib/os-autoinst/backend/baseclass.pm line 245.

[2019-02-21T23:54:15.127 CET] [debug] Destroying openQA-SUT-4 virtual machine
[2019-02-21T23:54:15.217 CET] [debug] Connection to root@s390p8.suse.de established
[2019-02-21T23:54:15.296 CET] [debug] Command's stdout:


[2019-02-21T23:54:15.296 CET] [debug] Command's stderr:
error: Failed to destroy domain openQA-SUT-4
error: Requested operation is not valid: domain is not running

[2019-02-21T23:54:15.296 CET] [debug] Command executed: virsh  destroy openQA-SUT-4, ret=1
[2019-02-21T23:54:15.387 CET] [debug] Connection to root@s390p8.suse.de established
[2019-02-21T23:54:15.464 CET] [debug] Command's stdout:
Domain openQA-SUT-4 has been undefined


[2019-02-21T23:54:15.464 CET] [debug] Command executed: virsh  undefine --snapshots-metadata openQA-SUT-4, ret=0
last frame

Reproducible

Fails what seems like more and more lately

Expected result

Last good: 165.1

Further details

Always latest result in this scenario: latest


Related issues 6 (1 open5 closed)

Related to openQA Tests - action #46964: [functional][u][s390x] test fails in the middle of execution (not installation) as incomplete with "half-open socket?" – connection to machine vanished?Resolvedokurz2019-02-01

Actions
Related to openQA Tests - action #46394: [sle][s390x][spvm][kvm][sporadic] test fails in various modules to login to svirt console (or system is not up yet)Workable

Actions
Related to openQA Tests - action #33202: [sle][functional][s390x][zkvm][u][hard] test fails in boot_to_desktop - still insufficient error reporting, black screen with mouse cursor - we all hate it (was: I hate it)Resolvedmgriessmeier2018-03-132018-08-14

Actions
Related to openQA Tests - action #49958: [functional][u][s390x] test fails in reboot_after_installation - Failed to destroy domain openQA-SUT-Rejectedokurz2019-04-03

Actions
Has duplicate openQA Tests - action #48284: [sle][migration][SLE15SP1]test fails in reboot_after_installation - Backend process diedRejected2019-02-22

Actions
Blocked by openQA Tests - action #48170: [functional][u][svirt][xen] SUTs are not able to reach SUSE network, e.g. failed to reach proxy.scc.suse.deResolvedxlai2019-02-21

Actions
Actions

Also available in: Atom PDF