QA » openQA Project » openQA Tests

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');

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);

I will double check with x86_64 platform and plan to file a bug to see if it is by design.

https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/15482