Following installation using Fedora-Workstation-Live-x86_64-39-20231009.n.0.iso, and subsequent dnf update a new kernel is installed and I see:
dnf update
kdump: For kernel=/boot/vmlinuz-6.5.6-300.fc39.x86_64, crashkernel=1G-4G:192M,4G-64G:256M,64G-:512M now. Please reboot the system for the change to take effet. Note if you don't want kexec-tools to manage the crashkernel kernel parameter, please set auto_reset_crashkernel=no in /etc/kdump.conf.
Indeed the 6.5.6 kernel entry is modified as described to enable kdump persistently. I don't see a feature change for this behavior. kexec-tools is installed, removing it removes a bunch of stuff we've had in Workstation for a while so it seems there is a change in kexec-tools to enable kdump by default.
kexec-tools
@jforbes Any idea if this is intended?
https://bugzilla.redhat.com/show_bug.cgi?id=2243068
I'm confused what's actually causing this behavior in Fedora 39. The /etc/kdump.conf in Fedora 38 contains the same setting: auto_reset_crashkernel yes
/etc/kdump.conf
auto_reset_crashkernel yes
Tentative fix is being tested, thanks @adamwill - closing this issue and will continue to track on the QA side.
Metadata Update from @chrismurphy: - Issue untagged with: meeting-request - Issue assigned to chrismurphy - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Thanks for picking up on this, @chrismurphy !
Reopening since the bug is not fixed.
I created this ticket to request that FESCo designate this as a special F39 blocker.
Metadata Update from @catanzaro: - Issue status updated to: Open (was: Closed)
We don't need to track this ourselves anymore because it is accepted blocker. Also, it's fixed.
Metadata Update from @catanzaro: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.