https://bugzilla.suse.com/show_bug.cgi?id=1226676 https://bugzilla.suse.com/show_bug.cgi?id=1226676#c7 Jiri Bohac <jbohac@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(rbrown@suse.com) CC| |rbrown@suse.com --- Comment #7 from Jiri Bohac <jbohac@suse.com> --- By default kdump relies on the /boot/vmlinuz symlink (or other image name variants on non-x86 archs). This points to the last installeed kernel. When a specific kernel version is requested by setting KDUMP_KERNELVER=xxx then it relies on the /boot/vmlinuz-xxx symlink. These links have always been created by the kernel's %post scriplet, which calls /usr/lib/module-init-tools/kernel-scriptlets/rpm-post This script used to be provided by the suse-module-tools-scriptlets subpackage. This is where the links are created: https://github.com/openSUSE/suse-module-tools/blob/790fe7ce0eb9db37932c65161... When I installe with sdboot, sdbootutil-rpm-scriptlets is installed instead of suse-module-tools-scriptlets and no such symlinks are created. One way of fixing this would be to create the symlinks in sdbootutil-rpm-scriptlets. Another way would be for kdump to look for the kernels elsewhere. To me the post scriplet seems to be an ideal place to deal with this, without kdump having to embed knowledge of the location of kernel images which could be fragile. Could the links be added to sdbootutil-rpm-scriptlets? -- You are receiving this mail because: You are on the CC list for the bug.