Project

General

Profile

Actions

action #135350

closed

[qe-core] test fails in handle_reboot

Added by dvenkatachala about 1 year ago. Updated about 1 year ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Bugs in existing tests
Target version:
Start date:
2023-09-07
Due date:
% Done:

0%

Estimated time:
Difficulty:

Description

Observation

openQA test in sle-15-SP4-Server-DVD-Incidents-Minimal-s390x-Build:30560:dtb-armv7l-qam-minimal@s390x-zVM-vswitch-l2 in
handle_reboot

[2023-09-06T18:55:54.887797+02:00] [debug] [pid:16402] tests/installation/handle_reboot.pm:24 called utils::reconnect_mgmt_console -> lib/utils.pm:1743 called testapi::select_console
[2023-09-06T18:55:54.887972+02:00] [debug] [pid:16402] <<< testapi::select_console(testapi_console="iucvconn")
[2023-09-06T18:55:54.888664+02:00] [debug] [pid:16403] <<< backend::baseclass::new_ssh_connection(hostname="s390qa102.qa.suse.de", username="root", password="SECRET")
[2023-09-06T18:55:54.890794+02:00] [debug] [pid:16403] Could not connect to root@s390qa102.qa.suse.de, Retrying after some seconds...
[2023-09-06T18:56:04.892136+02:00] [debug] [pid:16403] Could not connect to root@s390qa102.qa.suse.de, Retrying after some seconds...
[2023-09-06T18:56:14.893619+02:00] [debug] [pid:16403] Could not connect to root@s390qa102.qa.suse.de, Retrying after some seconds...
[2023-09-06T18:56:24.894973+02:00] [debug] [pid:16403] Could not connect to root@s390qa102.qa.suse.de, Retrying after some seconds...
[2023-09-06T18:56:34.896291+02:00] [debug] [pid:16403] Could not connect to root@s390qa102.qa.suse.de, Retrying after some seconds...

Reproducible

Fails since (at least) Build :30560:dtb-armv7l

Expected result

Last good: :30055:zypper (or more recent)

Further details

Always latest result in this scenario: latest

Actions #1

Updated by dvenkatachala about 1 year ago

  • Target version set to QE-Core: Ready
Actions #2

Updated by dvenkatachala about 1 year ago

  • Status changed from New to In Progress
  • Assignee set to dvenkatachala
Actions #3

Updated by dvenkatachala about 1 year ago

  • Status changed from In Progress to Resolved

The issue was due to the wrong needle addition.

Actions

Also available in: Atom PDF