Bugzilla – Bug 1228242
[Build 20240722] installation enables kdump, but configuration is incomplete
Last modified: 2024-07-24 07:32:22 UTC
## Observation It seems like yast is enabling the kdump services, but the command line parameters to are not properly set from y2log: 2024-07-23 07:21:11 <1> install(3770) [Ruby] yast/wfm.rb(run_client):341 Call client /mounts/mp_0001/usr/share/YaST2/clients/kdump_finish.rb 2024-07-23 07:21:11 <1> install(3770) [Ruby] installation/finish_client.rb(run):51 Called Y2Kdump::Clients::Finish.run with Write 2024-07-23 07:21:11 <1> install(3770) [Ruby] modules/Kdump.rb(log_settings_censoring_passwords):376 -------------KDUMP_SETTINGS------------------- 2024-07-23 07:21:11 <1> install(3770) [Ruby] modules/Kdump.rb(log_settings_censoring_passwords):377 kdump configuration for writing; here with censored passwords: {"KDUMP_KERNELVER"=>"", "KDUMP_CPUS"=>"1", "KDUMP_COMMANDLINE"=>"", "KDUMP_COMMANDLINE_APPEND"=>"", "KDUMP_AUTO_RESIZE"=>"false", "KEXEC_OPTIONS"=>"", "KDUMP_IMMEDIATE_REBOOT"=>"true", "KDUMP_TRANSFER"=>"", "KDUMP_SAVEDIR"=>"********", "KDUMP_KEEP_OLD_DUMPS"=>"0", "KDUMP_FREE_DISK_SIZE"=>"64", "KDUMP_VERBOSE"=>"0", "KDUMP_DUMPLEVEL"=>"31", "KDUMP_DUMPFORMAT"=>"compressed", "KDUMP_CONTINUE_ON_ERROR"=>"true", "KDUMP_REQUIRED_PROGRAMS"=>"", "KDUMP_PRESCRIPT"=>"", "KDUMP_POSTSCRIPT"=>"", "KDUMP_NETCONFIG"=>"auto", "KDUMP_NET_TIMEOUT"=>"30", "KDUMP_SMTP_SERVER"=>"", "KDUMP_SMTP_USER"=>"", "KDUMP_SMTP_PASSWORD"=>"********", "KDUMP_NOTIFICATION_TO"=>"", "KDUMP_NOTIFICATION_CC"=>"", "KDUMP_HOST_KEY"=>""} 2024-07-23 07:21:11 <1> install(3770) [Ruby] modules/Kdump.rb(log_settings_censoring_passwords):378 --------------------------------------------- 2024-07-23 07:21:11 <1> install(3770) [Ruby] modules/Kdump.rb(Chmod):234 Command: /bin/chmod 644 /etc/sysconfig/kdump finish successful. 2024-07-23 07:21:11 <1> install(3770) [Ruby] modules/Package.rb(IsTransactionalSystem):447 root in mounts {"file"=>"/mnt", "freq"=>0, "mntops"=>"rw,relatime,discard=async,space_cache=v2,subvolid=266,subvol=/@/.snapshots/1/snapshot", "passno"=>0, "spec"=>"/dev/vda2", "vfstype"=>"btrfs"} 2024-07-23 07:21:11 <1> install(3770) [Ruby] modules/Kdump.rb(update_initrd_with):421 Running command: mkdumprd >> /var/log/YaST2/y2logmkinitrd 2>&1 2024-07-23 07:21:19 <1> install(3770) [Ruby] modules/Kdump.rb(crash_kernel_values):1166 built crashkernel values are ["307M,high"] 2024-07-23 07:21:19 <1> install(3770) [Ruby] modules/Kdump.rb(crash_xen_kernel_values):1198 built xen crashkernel values are ["307M\\<4G"] 2024-07-23 07:21:19 <2> install(3770) [Ruby] modules/Bootloader.rb(modify_kernel_params):404 recovery flavor is deprecated and not set 2024-07-23 07:21:19 <1> install(3770) [Ruby] modules/Kdump.rb(WriteKdumpBootParameter):505 [kdump] (WriteKdumpBootParameter) adding crashkernel options with values: ["307M,high"] 2024-07-23 07:21:19 <1> install(3770) [Ruby] modules/Kdump.rb(WriteKdumpBootParameter):509 [kdump] (WriteKdumpBootParameter) adding xen crashkernel options with values: ["307M\\<4G"] 2024-07-23 07:21:19 <1> install(3770) [Ruby] modules/Service.rb(Enable):113 Enabling service 'kdump' 2024-07-23 07:21:19 <1> install(3770) [Ruby] yast2/systemctl.rb(execute):41 systemctl is-enabled kdump.service 2024-07-23 07:21:19 <1> install(3770) [Ruby] yast2/systemctl.rb(execute):41 systemctl enable kdump.service 2024-07-23 07:21:19 <3> install(3770) [bash] ShellCommand.cc(shellcommand):78 Created symlink /etc/systemd/system/multi-user.target.wants/kdump.service -> /usr/lib/systemd/system/kdump.service. 2024-07-23 07:21:19 <3> install(3770) [bash] ShellCommand.cc(shellcommand):78 Created symlink /etc/systemd/system/multi-user.target.wants/kdump-early.service -> /usr/lib/systemd/system/kdump-early.service. 2024-07-23 07:21:19 <3> install(3770) [bash] ShellCommand.cc(shellcommand):78 Created symlink /etc/systemd/system/multi-user.target.wants/kdump-notify.service -> /usr/lib/systemd/system/kdump-notify.service. 2024-07-23 07:21:19 <1> install(3770) [Ruby] yast2/systemctl.rb(execute):41 systemctl is-enabled kdump.service 2024-07-23 07:21:19 <1> install(3770) [Interpreter] clients/inst_finish.rb:117 Called YaST client returned. 2024-07-23 07:21:19 <1> install(3770) [Ruby] modules/Hooks.rb(execute):167 Executing hook 'after_kdump_finish' 2024-07-23 07:21:19 <1> install(3770) [Ruby] modules/Hooks.rb(execute):167 Executing hook 'before_bootloader_finish' 2024-07-23 07:21:19 <1> install(3770) [Interpreter] clients/inst_finish.rb:117 Calling YaST client bootloader_finish A somewhat interesting part seems to be 2024-07-23 07:21:19 <1> install(3770) [Ruby] modules/Kdump.rb(WriteKdumpBootParameter):505 [kdump] (WriteKdumpBootParameter) adding crashkernel options with values: ["307M,high"] yet the kernel command line parameter is apparently missing, as the service startup fails with Jul 23 07:45:28 localhost load.sh[817]: Memory for crashkernel is not reserved Jul 23 07:45:28 localhost load.sh[817]: Please reserve memory by passing"crashkernel=Y@X" parameter to kernel Jul 23 07:45:28 localhost load.sh[817]: Then try to loading kdump kernel Jul 23 07:45:28 localhost load.sh[753]: kexec failed. full log tarball at https://openqa.opensuse.org/tests/4355988/file/logs_from_installation_system-y2logs.tar.bz2 openQA test in scenario microos-Tumbleweed-DVD-x86_64-microos-sdboot@uefi_virtio-2G fails in [journal_check](https://openqa.opensuse.org/tests/4355988/modules/journal_check/steps/60) ## Test suite description MicroOS, but use systemd-boot as bootloader. Needs UEFI. ## Reproducible Fails since (at least) Build [20240719](https://openqa.opensuse.org/tests/4351330) ## Expected result Last good: (unknown) (or more recent) ## Further details Always latest result in this scenario: [latest](https://openqa.opensuse.org/tests/latest?arch=x86_64&distri=microos&flavor=DVD&machine=uefi_virtio-2G&test=microos-sdboot&version=Tumbleweed)
Is a dup of this one? https://bugzilla.suse.com/show_bug.cgi?id=1226676
(In reply to Alberto Planas Dominguez from comment #1) > Is a dup of this one? https://bugzilla.suse.com/show_bug.cgi?id=1226676 Might be related, but does not directly look like a DUP. i.e installation passes without error, mkdumprd (from kdump 2.0.7 in this case) has run without error
same issue: bsc#1214938
There is a PR [1] to avoid proposing Kdump if systemd-boot is used for bootloader. But it seems the submission failed. Josef, Schubi, could you please have a look? Thanks! [1] https://github.com/yast/yast-kdump/pull/138
The bsc number has been missed. Submitted again: https://build.opensuse.org/request/show/1189320