action #65474
closed[qe-core][sle][functional] test fails in kdump_and_crash - previous traces on screen
0%
Description
Observation¶
Related bug: https://bugzilla.suse.com/show_bug.cgi?id=1169881
openQA test in scenario sle-15-SP2-Online-s390x-extra_tests_textmode@s390x-kvm-sle12 fails in
kdump_and_crash
Suggestion¶
- Make sure that test dies after wait_serial timeout (see https://github.com/os-autoinst/os-autoinst-distri-opensuse/blob/master/lib/opensusebasetest.pm#L686)
- Increase the timeout for zKVM for rebooting
Reproducible¶
Fails since (at least) Build 161.1
Expected result¶
Last good: (unknown) (or more recent)
Further details¶
Always latest result in this scenario: latest
Investigations¶
it looks like kdump just gone suddenly before it got configured completely. It might be a product issue.
Updated by SLindoMansilla almost 4 years ago
- Description updated (diff)
- Status changed from New to Workable
- Target version set to Milestone 30
- Estimated time set to 42.00 h
Updated by zluo almost 4 years ago
- Status changed from Workable to In Progress
- Assignee set to zluo
take over
Updated by zluo almost 4 years ago
Bug 1169881 [Build 179.1][zKVM] openQA test fails in kdump_and_crash - Kernel panic
So we need to handle this with softfail later in power_actions_utils.pm:
# sometimes s390x with backend svirt needs more time to shutdown or encouter kernel panic, see bsc#1169881
if (is_s390x && check_var('BACKEND', 'svirt')) {
$soft_fail_data = {bugref => '1169881', soft_timeout => 90, timeout => $shutdown_timeout *= 3};
}
Let's just do suggestion #1 for now:
Make sure that test dies after wait_serial timeout (see https://github.com/os-autoinst/os-autoinst-distri-opensuse/blob/master/lib/opensusebasetest.pm#L686)
Updated by zluo almost 4 years ago
https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/10065
see https://progress.opensuse.org/issues/65474
veification partly for "not find GRUB screen":
https://openqa.suse.de/tests/4141066#step/kdump_and_crash/86
since there is call trace there and SUT is not able to go further, it means no workaround or softail is possible. set as blocked for now and wait possible fixing of the product issue.
Updated by tjyrinki_suse over 3 years ago
- Subject changed from [sle][functional][u] test fails in kdump_and_crash - previous traces on screen to [qe-core][sle][functional] test fails in kdump_and_crash - previous traces on screen
Updated by zluo over 3 years ago
- Status changed from Blocked to In Progress
https://bugzilla.suse.com/show_bug.cgi?id=1169881 got resolved, so checking the issue on openQA.
Updated by zluo over 3 years ago
- Status changed from In Progress to Resolved
https://openqa.suse.de/tests/5024915#next_previous no issue anymore.