action #67144
closedopenQA backend died on "problem with virsh: cmd: 'virsh console openQA-SUT-3 console1', output of script wrapper
0%
Description
Observation¶
openQA test in scenario sle-15-SP2-Online-s390x-fips_ker_mode_tests_crypt_tool@s390x-kvm-sle12 fails in
git
The error message:
[
failed
Failed
System I/O status:
Test died: problem with virsh: cmd: 'virsh console openQA-SUT-2 console1', output of script wrapper: 'Script started on 2020-05-21 20:59:11+02:00 []¶
Connected to domain openQA-SUT-2
Escape character is ]
error: operation failed: Active console session exists for this domain
CONSOLE_EXIT_iuAe0ASnOOE_Fodl: 1
Script done on 2020-05-21 20:59:11+02:00 [COMMAND_EXIT_CODE="0"]
') at /usr/lib/os-autoinst/backend/svirt.pm line 325.
]
Test suite description¶
Maintainer: bchou@suse.com
Reproducible¶
Fails since (at least) Build 93.1
Expected result¶
Last good: (unknown) (or more recent)
It passed at least on last build (195.1):
https://openqa.nue.suse.com/tests/4247401#step/git/2
Further details¶
Always latest result in this scenario: latest
It makes selinux-sestatus test module failed too:
https://openqa.nue.suse.com/tests/4268112#step/sestatus/59
Updated by llzhao almost 4 years ago
NOTE: error: operation failed: Active console session exists for this domain
Updated by llzhao almost 4 years ago
- Project changed from openQA Tests to openQA Project
- Category changed from Bugs in existing tests to Regressions/Crashes
Updated by rfan1 almost 4 years ago
$self->select_serial_terminal;
Can we consider to use "select_console 'root-console'"
Updated by llzhao almost 4 years ago
rfan1 wrote:
$self->select_serial_terminal;
Can we consider to use "select_console 'root-console'"
Can but I would like not to. I had explained the reason about choosing "select_serial_terminal" in our daily scrum meeting.
You might forgot :).
Updated by llzhao almost 4 years ago
Got response from tool group they will not check/fix this poo recently.
So QA prefer select_console 'root-console'" at this moment.
Updated by okurz almost 4 years ago
- Category changed from Regressions/Crashes to Support
- Status changed from New to Resolved
- Assignee set to okurz
I assume you found a way working for you? Considering that also the latest job in the reference test scenario https://openqa.nue.suse.com/tests/4361215 does not fail in the same way as originally reported I guess we can call this "Resolved" as a support case.