What were you trying to do that didn't work?

According to chapter 22.6.1 of the Automatically Installing RHEL
document (https://docs.redhat.com/en/documentation/red_hat_enterprise_linux/9/html/automatically_installing_rhel/kickstart-commands-and-options-reference_rhel-installer#addon-com_redhat_kdump_kickstart-commands-for-addons-supplied-with-the-rhel-installation-program), one can disable kdump during a kickstart by having this in the kickstart configuration file:

%addon com_redhat_kdump --disable
%end

Yet, including that fails to work once the machine is updated.

What is the impact of this issue to you?

Have to stop & disable the service, remove the kexec-tools RPM before any new kernels are installed via a 'dnf -y update'.

How reproducible is this bug?:

Always.

Steps to reproduce

Kickstart a machine with this in the kickstart configuration file:

%addon com_redhat_kdump --disable
%end

Either in the kickstart's %post section, or after the kickstarted machine boots up for the 1st time, run 'dnf -y update' when a new kernel is available.

Expected results

No crashkernel memory is reserved by the newly installed kernel and the kexec-tools RPM is not installed.

Actual results

Memory is still reserved:

[root@test ~]# cat /proc/cmdline
BOOT_IMAGE=(hd0,msdos1)/vmlinuz-5.14.0-611.16.1.el9_7.x86_64 root=/dev/mapper/s618-root ro resume=/dev/mapper/s618-swap rd.lvm.lv=s618/root rd.lvm.lv=s618/swap crashkernel=1G-2G:192M,2G-64G:256M,64G-:512M

...the kexec-tools RPM is installed:

[root@test ~]# rpm -q kexec-tools
kexec-tools-2.0.29-10.el9.x86_64

...and the kdump service is enabled and started:

[root@test ~]# systemctl status kdump.service
● kdump.service - Crash recovery kernel arming
Loaded: loaded (/usr/lib/systemd/system/kdump.service; enabled; preset: enabled)
Active: active (exited) since Tue 2025-12-30 17:03:34 EST; 8min ago
Process: 902 ExecCondition=/bin/sh -c grep -q -e "crashkernel" -e "fadump" /proc/cmdline (c>
Process: 917 ExecStart=/usr/bin/kdumpctl start (code=exited, status=0/SUCCESS)
Main PID: 917 (code=exited, status=0/SUCCESS)
CPU: 11.818s