Project

General

Profile

Actions

action #100626

closed

[qem][y] test fails in bootloader_start

Added by martinsmac over 2 years ago. Updated about 1 month ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
Bugs in existing tests
Target version:
-
Start date:
2021-10-08
Due date:
% Done:

0%

Estimated time:
Difficulty:

Description

Observation

openQA test in scenario sle-15-SP1-Server-DVD-Updates-s390x-qam-gnome@s390x-kvm-sle12 fails in
bootloader_start

Test suite description

Testsuite maintained at https://gitlab.suse.de/qa-maintenance/qam-openqa-yml.

Reproducible

Fails since (at least) Build 20211008-1 (current job)

Expected result

Last good: 20211007-2 (or more recent)

Further details

Always latest result in this scenario: latest

Error reported:

Test died: {

"json_cmd_token" => "KpHpvPSh",
"cmd" => "backend_proxy_console_call",
"function" => "define_and_start",
"console" => "svirt",
"args" => [],
"wantarray" => undef
}
virsh start failed at /usr/lib/os-autoinst/consoles/sshVirtsh.pm line 535.
at /usr/lib/os-autoinst/backend/console_proxy.pm line 53.
backend::console_proxy::ANON(undef) called at sle/tests/installation/bootloader_zkvm.pm line 78
bootloader_zkvm::run(bootloader_start=HASH(0x1001e338a58)) called at sle/tests/installation/bootloader_start.pm line 52
bootloader_start::run(bootloader_start=HASH(0x1001e338a58)) called at /usr/lib/os-autoinst/basetest.pm line 343
eval {...} called at /usr/lib/os-autoinst/basetest.pm line 337
basetest::runtest(bootloader_start=HASH(0x1001e338a58)) called at /usr/lib/os-autoinst/autotest.pm line 368

Actions #1

Updated by okurz about 2 years ago

  • Subject changed from [qem] test fails in bootloader_start to [qem][y] test fails in bootloader_start

assigning to "[y]" as test module maintainers

Actions #2

Updated by slo-gin about 1 year ago

This ticket was set to Normal priority but was not updated within the SLO period. Please consider picking up this ticket or just set the ticket to the next lower priority.

Actions #3

Updated by slo-gin about 1 month ago

This ticket was set to Normal priority but was not updated within the SLO period. Please consider picking up this ticket or just set the ticket to the next lower priority.

Actions #4

Updated by martinsmac about 1 month ago

  • Status changed from New to Closed
Actions

Also available in: Atom PDF