Actions
action #115589
closed[qe-core][sle15sp5][functional][s390x]test fails in kdump_and_crash
Status:
Resolved
Priority:
Normal
Assignee:
Category:
Bugs in existing tests
Target version:
Start date:
2022-08-22
Due date:
% Done:
100%
Estimated time:
3.00 h
Difficulty:
Tags:
Description
Observation¶
openQA test in scenario sle-15-SP5-Online-s390x-toolchain_zypper@s390x-kvm-sle12 fails in
kdump_and_crash
Test suite description¶
Maintainer: QE Core, mnowak
Install toolchain packages and test the toolchain. Uses a more powerful machine configuration.
Reproducible¶
Fails since (at least) Build 9.1
Expected result¶
Last good: (unknown) (or more recent)
Further details¶
Always latest result in this scenario: latest
Updated by rfan1 over 2 years ago
- Subject changed from [qe-core][sle15sp5]test fails in kdump_and_crash to [qe-core][sle15sp5][s390x]test fails in kdump_and_crash
There might be some changes for sle15sp5 on kdump configuration.
We may still sent key again here even $expect_restart_info == 0
send_key('alt-o');
if ($expect_restart_info == 1) {
my @tags = qw(yast2-kdump-restart-info os-prober-warning);
do {
assert_screen(\@tags, timeout => 180);
handle_warning_install_os_prober() if match_has_tag('os-prober-warning');
} until (match_has_tag('yast2-kdump-restart-info'));
send_key('alt-o');
Updated by rfan1 over 2 years ago
- Assignee set to rfan1
Added some workaround and case can pass now https://openqa.suse.de/tests/9371214
diff --git a/lib/kdump_utils.pm b/lib/kdump_utils.pm
index 22c9feee9..e05d10aba 100644
--- a/lib/kdump_utils.pm
+++ b/lib/kdump_utils.pm
@@ -195,6 +195,10 @@ sub activate_kdump {
} until (match_has_tag('yast2-kdump-restart-info'));
send_key('alt-o');
}
+
+ # Duo to poo#115589, we may need double confirm the 'yast2-kdump-restart-info'
+ # for sle15sp5 to continue even kdump service is active.
+ send_key('alt-o') if (check_screen('yast2-kdump-restart-info', 180) && is_sle('=15-sp5') && is_s390x);
Updated by rfan1 over 2 years ago
- Status changed from New to In Progress
- % Done changed from 0 to 20
- Estimated time set to 3.00 h
I will double check with x86_64 platform and plan to file a bug to see if it is by design.
Updated by rfan1 over 2 years ago
Updated by rfan1 over 2 years ago
- Subject changed from [qe-core][sle15sp5][s390x]test fails in kdump_and_crash to [sle15sp5][functional][s390x]test fails in kdump_and_crash
Updated by rfan1 over 2 years ago
- Subject changed from [sle15sp5][functional][s390x]test fails in kdump_and_crash to [qe-core][sle15sp5][functional][s390x]test fails in kdump_and_crash
Updated by rfan1 over 2 years ago
- Status changed from In Progress to Feedback
- % Done changed from 20 to 90
Updated by rfan1 over 2 years ago
- Status changed from Feedback to Resolved
- % Done changed from 90 to 100
Actions