Bug 1202738 - [Build 15.2][aarch64] openQA test fails in kdump_and_crash, kdump service fails to start
[Build 15.2][aarch64] openQA test fails in kdump_and_crash, kdump service fai...
Status: CONFIRMED
Classification: openSUSE
Product: PUBLIC SUSE Linux Enterprise Server 15 SP5
Classification: openSUSE
Component: YaST2
unspecified
aarch64 SLES 15
: P2 - High : Normal
: ---
Assigned To: YaST Team
https://openqa.suse.de/tests/9379906/...
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2022-08-25 07:23 UTC by Richard Fan
Modified: 2022-09-08 02:01 UTC (History)
3 users (show)

See Also:
Found By: openQA
Services Priority:
Business Priority:
Blocker: Yes
Marketing QA Status: ---
IT Deployment: ---


Attachments
kdump_aarch64 (36.98 KB, image/png)
2022-08-25 07:23 UTC, Richard Fan
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Richard Fan 2022-08-25 07:23:36 UTC
Created attachment 861059 [details]
kdump_aarch64

## Observation

openQA test in scenario sle-15-SP5-Online-aarch64-toolchain_zypper@aarch64 fails in
[kdump_and_crash](https://openqa.suse.de/tests/9379906/modules/kdump_and_crash/steps/55)

## 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](https://openqa.suse.de/tests/9304874)


## Expected result

Last good: (unknown) (or more recent)


## Further details

Always latest result in this scenario: [latest](https://openqa.suse.de/tests/latest?arch=aarch64&distri=sle&flavor=Online&machine=aarch64&test=toolchain_zypper&version=15-SP5)

========================================

I can reproduce the issue on my local setup as well.

1. yast2 kdump
2. send key "alt+u" to enable kdump service
3. send key "alt+o" when I get “To apply changes a reboot is necessary"
4. reboot the system
5. check the kdump services
# 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 Thu 2022-08-25 03:09:00 EDT; 12min ago
   Main PID: 1250 (code=exited, status=1/FAILURE)

Aug 25 03:09:00 susetest load.sh[1250]: Memory for crashkernel is not reserved
Aug 25 03:09:00 susetest load.sh[1250]: Please reserve memory by passing"crashkernel=X@Y" parameter to kernel
Aug 25 03:09:00 susetest load.sh[1250]: Then try to loading kdump kernel
Aug 25 03:09:00 susetest load.sh[1250]: Memory for crashkernel is not reserved
Aug 25 03:09:00 susetest load.sh[1250]: Please reserve memory by passing"crashkernel=X@Y" parameter to kernel
Aug 25 03:09:00 susetest load.sh[1250]: Then try to loading kdump kernel
Aug 25 03:09:00 susetest kdump[4447]: FAILED to load kdump kernel: /sbin/kexec -p /boot/Image-5.14.21-150400.24.18-default --append=" plymouth.ignore-serial-consoles console=ttyAMA0 console=tty kernel.softlockup_panic=1 security=apparmor>
                                      Please reserve memory by passing"crashkernel=X@Y" parameter to kernel
                                      Then try to loading kdump kernel
Aug 25 03:09:00 susetest systemd[1]: kdump.service: Main process exited, code=exited, status=1/FAILURE
Aug 25 03:09:00 susetest systemd[1]: kdump.service: Failed with result 'exit-code'.
Aug 25 03:09:00 susetest systemd[1]: Failed to start Load kdump kernel and initrd.
# cat /proc/cmdline 
BOOT_IMAGE=/boot/Image-5.14.21-150400.24.18-default root=UUID=fa8c06ab-5235-463b-8f7a-5fddabfebb55 splash=silent plymouth.ignore-serial-consoles console=ttyAMA0 console=tty kernel.softlockup_panic=1 security=apparmor mitigations=auto
=============
One thing interested me is that I can't adjust the kdump memory size, please see attached file.
Comment 2 Ming Li 2022-09-08 02:01:33 UTC
I think this is the same bug, after yast kdump in the grub.cfg file the setting GRUB_CMDLINE_LINUX_DEFAULT without crashkernel= in value.
http://openqa.nue.suse.com/tests/9456589#step/yast2_kdump/30