Project

General

Profile

Actions
Copy link

action #49466

closed

[functional][u][opensuse] test fails in kdump_and_crash TW ppc64le "No suitable kdump kernel found"

Added by michel_mno about 5 years ago. Updated over 4 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
szarate
Category:
Bugs in existing tests
Target version:
SUSE QA - Milestone 26
Start date:
2019-03-19
Due date:
% Done:

0%

Estimated time:
Difficulty:

Description

test fails in kdump_and_crash TW ppc64le "No suitable kdump kernel found"

reported error message in openQA window and in serial0.txt file

systemctl status kdump
● kdump.service - Load kdump kernel and initrd
   Loaded: loaded (/usr/lib/systemd/system/kdump.service; enabled; vendor preset: disabled)
   Active: failed (Result: exit-code) since Mon 2019-03-18 23:24:35 EDT; 46s ago
  Process: 2920 ExecStart=/lib/kdump/load.sh --update (code=exited, status=6)
 Main PID: 2920 (code=exited, status=6)

Mar 18 23:24:32 susetest systemd[1]: Starting Load kdump kernel and initrd...
Mar 18 23:24:32 susetest load.sh[2920]: No suitable kdump kernel found.
Mar 18 23:24:33 susetest load.sh[2920]: Perl-Bootloader: 2019-03-18 23:24:33 <3> libpbl-1962.1 Core::GRUB2::GrubDev2UnixDev.256: Error: did not find a match for hd0 in the device map
Mar 18 23:24:33 susetest load.sh[2920]: Perl-Bootloader: 2019-03-18 23:24:33 <3> libpbl-3179.1 Core::GRUB2::GrubDev2UnixDev.256: Error: did not find a match for hd0 in the device map
Mar 18 23:24:35 susetest load.sh[2920]: No kdump initial ramdisk found. Tried to locate .
Mar 18 23:24:35 susetest systemd[1]: kdump.service: Main process exited, code=exited, status=6/NOTCONFIGURED
Mar 18 23:24:35 susetest systemd[1]: kdump.service: Failed with result 'exit-code'.
Mar 18 23:24:35 susetest systemd[1]: Failed to start Load kdump kernel and initrd.

I do not know what is missing here, this test never passed in o3 for ppc64le TW.
There was a previous issue#33376 reporting test passed for SLE-15 ppc64le.
https://progress.opensuse.org/issues/33376#note-65

Observation

openQA test in scenario opensuse-Tumbleweed-DVD-ppc64le-extra_tests_in_textmode@ppc64le fails in
kdump_and_crash

Test suite description

Maintainer: okurz@suse.de

Mainly console extratest.

Reproducible

Fails since (at least) Build 20180813

Expected result

Last good: (unknown) (or more recent)

Further details

Always latest result in this scenario: latest

Actions
Copy link
 #1

Updated by SLindoMansilla about 5 years ago

  • Subject changed from test fails in kdump_and_crash TW ppc64le "No suitable kdump kernel found" to [functional][opensuse] test fails in kdump_and_crash TW ppc64le "No suitable kdump kernel found"

As a result of backlog triaging (see https://progress.opensuse.org/projects/openqatests/wiki#ticket-backlog-triaging for more information).

Please, feel free to adjust the category or the "[label]" if you think different.

Actions
Copy link
 #2

Updated by SLindoMansilla about 5 years ago

  • Subject changed from [functional][opensuse] test fails in kdump_and_crash TW ppc64le "No suitable kdump kernel found" to [functional][u][opensuse] test fails in kdump_and_crash TW ppc64le "No suitable kdump kernel found"
Actions
Copy link
 #3

Updated by okurz about 5 years ago

This is an autogenerated message for openQA integration by the openqa_review script:

This bug is still referenced in a failing openQA test: extra_tests_in_textmode
https://openqa.opensuse.org/tests/892495

Actions
Copy link
 #4

Updated by okurz about 5 years ago

This is an autogenerated message for openQA integration by the openqa_review script:

This bug is still referenced in a failing openQA test: extra_tests_in_textmode
https://openqa.opensuse.org/tests/892495

Actions
Copy link
 #5

Updated by michel_mno about 5 years ago

Still similar failure with last snapshot 20190505:
https://openqa.opensuse.org/tests/925219#step/kdump_and_crash/46

I do not know if functional kdump failure or something from openQA test.
I still have "No suitable kdump kernel found." as extracted below despite the correct debuginfo kernel packages as per zypper.log 

F0ZS5
● kdump.service - Load kdump kernel and initrd
   Loaded: loaded (/usr/lib/systemd/system/kdump.service; enabled; vendor preset: disabled)
   Active: failed (Result: exit-code) since Mon 2019-05-06 05:06:17 EDT; 19min ago
  Process: 2888 ExecStart=/lib/kdump/load.sh --update (code=exited, status=6)
 Main PID: 2888 (code=exited, status=6)

May 06 05:06:14 susetest systemd[1]: Starting Load kdump kernel and initrd...
May 06 05:06:14 susetest load.sh[2888]: No suitable kdump kernel found.
May 06 05:06:17 susetest load.sh[2888]: No kdump initial ramdisk found. Tried to locate .
May 06 05:06:17 susetest systemd[1]: kdump.service: Main process exited, code=exited, status=6/NOTCONFIGURED
May 06 05:06:17 susetest systemd[1]: kdump.service: Failed with result 'exit-code'.
May 06 05:06:17 susetest systemd[1]: Failed to start Load kdump kernel and initrd.
SCRIPT_FINISHEDF0ZS5-0-
Actions
Copy link
 #6

Updated by michel_mno almost 5 years ago

  • Status changed from New to In Progress

Reported "No suitable kdump kernel found" caused by missing CONFIG_RELOCATABLE in PowerPC kernel config.

Actions
Copy link
 #7

Updated by zluo almost 5 years ago

  • Assignee set to zluo
  • Target version set to Milestone 25

take over

Actions
Copy link
 #8

Updated by zluo almost 5 years ago

bsc#1021484 -- fail to create kdump initrd
this is the issue which causes test failed.

but in kdump_utils.pm we have:

sub kdump_is_active {
# make sure kdump is enabled after reboot
my $status;
for (1 .. 10) {
$status = script_output('systemctl status kdump ||:');
if ($status =~ /No kdump initial ramdisk found/) {
record_soft_failure 'bsc#1021484 -- fail to create kdump initrd';
systemctl 'restart kdump';
next;
}
elsif ($status =~ /Active: active/) {
return 1;
}
elsif ($status =~ /Active: activating/) {
diag "Service is activating, sleeping and looking again. Retry $_";
sleep 10;
next;
}
die "undefined state of kdump service";
}
}

systemctl 'restart kdump'; next; will still be executed which leads to failure later.

The test should stop and return with a softfail.

Comments already added to https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/7394

Actions
Copy link
 #9

Updated by zluo almost 5 years ago

need logs for bug report this issue:

https://openqa.opensuse.org/tests/934897#settings

Actions
Copy link
 #11

Updated by zluo almost 5 years ago

PR of michel_mno got merged and now need to verify the test run:
https://openqa.opensuse.org/tests/935802

Actions
Copy link
 #12

Updated by zluo almost 5 years ago

https://openqa.suse.de/tests/2896797#step/kdump_and_crash/47 shows the problem for sles now.

INFO: kdump mem size is not got changed, this needs to be checked as well.

Actions
Copy link
 #13

Updated by zluo almost 5 years ago

  • Assignee changed from zluo to szarate

https://openqa.opensuse.org/tests/935802/modules/kdump_and_crash/steps/1/src shows that changes from PR are not available yet.

@szarate as you wish, please take over.

Actions
Copy link
 #14

Updated by mgriessmeier almost 5 years ago

  • Target version changed from Milestone 25 to Milestone 26
Actions
Copy link
 #15

Updated by michel_mno almost 5 years ago

For TW ppc64le this issue is solved and is now followed by new issue
https://progress.opensuse.org/issues/53813

I do not know purpose of other updates where some refer to sles.

Actions
Copy link
 #16

Updated by szarate almost 5 years ago

  • Status changed from In Progress to Workable
Actions
Copy link
 #17

Updated by mgriessmeier over 4 years ago

  • Status changed from Workable to Resolved

michel_mno wrote:

For TW ppc64le this issue is solved and is now followed by new issue
https://progress.opensuse.org/issues/53813

I do not know purpose of other updates where some refer to sles.

resolving

Actions
Copy link

Also available in: Atom PDF