Description of problem:
Since currently crashkernel= will be handled in kdump anaconda addon we can safely remove rhcrashkernel-param callback.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
Dave, I guess you want this fixed on Fedora 21, right? If so, please change the Version field of this bug. Thanks!
anaconda-21.48.10-1.fc21 has been submitted as an update for Fedora 21.
Package anaconda-21.48.10-1.fc21, pykickstart-1.99.63-2.fc21, python-blivet-0.61.5-1.fc21:
* should fix your issue,
* was pushed to the Fedora 21 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing anaconda-21.48.10-1.fc21 pykickstart-1.99.63-2.fc21 python-blivet-0.61.5-1.fc21'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
anaconda-21.48.10-1.fc21, pykickstart-1.99.63-2.fc21, python-blivet-0.61.5-1.fc21 has been pushed to the Fedora 21 stable repository. If problems still persist, please make note of it in this bug report.
How exactly was this supposed to work with fedup upgrades? I have kdump that used to work and due to this change I believe, it no longer has the crashkernel commandline options. The kexec-tools-anaconda-addon was never installed. Maybe some other package needs to require it.
(In reply to Jonathan Briggs from comment #6)
> How exactly was this supposed to work with fedup upgrades? I have kdump that
> used to work and due to this change I believe, it no longer has the
> crashkernel commandline options. The kexec-tools-anaconda-addon was never
> installed. Maybe some other package needs to require it.
That's unrelated to this bug report. This bug report is about removing a piece of code from anaconda that now lives in the kdump-anaconda-addon. Upgrades, should, AFAICT preserve boot options like crashkernel and the same applies to installed packages, so that's a fedup bug, I think.
It is all related and affects multiple packages. The rhcrashkernel-param program got removed from kexec. The anaconda code that called it got removed and put in a plugin.
The code itself was a line in /etc/sysconfig/grub that checked for rhcrashkernel-param and called it.
So the boot options that fedup was supposed to preserve do not exist in the grub2 source files anywhere after these changes. fedup would need some kind of special check just for this issue. It would have to somehow know to add the anaconda plugin based on the previous existance of kexec.
Anaconda is not used during a fedup upgrade. This bug is about anaconda using rhcrashkernel-param during installation to set up the kexec parameters. This bug has nothing to do with upgrades.
Since kexec-tools removes the program in question, /usr/sbin/rhcrashkernel-param, you should file a new bug against kexec-tools to handle changing config files during the package upgrade.