Description of problem: When performing an anaconda upgrade from F10 -> F11 (anaconda-11.5.0.52), the upgrade bootloader choice is ignored. Anaconda seems to always install a new bootloader configuration. Version-Release number of selected component (if applicable): anaconda-11.5.0.52 How reproducible: Everytime Steps to Reproduce: Either 1) https://fedoraproject.org/wiki/QA:Testcase_Anaconda_Upgrade_Update_Bootloader or 2) https://fedoraproject.org/wiki/QA:Testcase_Anaconda_Upgrade_Skip_Bootloader Actual results: * Both cases result in a grub.conf with *only* the new kernel Expected results: For Update_Bootloader: * I expect to see a grub.conf with the old *and* new kernels? For Skip_Bootloader * I expect to see a grub.conf with *only* the old kernel Additional info:
*** This bug has been marked as a duplicate of bug 494103 ***
Reopening after discussion w/ clumens on #anaconda. The DUP'd bug#494103 appears to be an expected result (placed in needinfo). This issue is specific to upgrading F10 -> F11 using anaconda. During the upgrade, choosing to "skip bootloader configuration changes" results in a new bootloader configuration regardless.
This issue has been documented at https://fedoraproject.org/wiki/Common_F11_bugs#501063
This bug appears to have been reported against 'rawhide' during the Fedora 11 development cycle. Changing version to '11'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
What's happening here is that even though you're specifying that anaconda should not update the bootloader config, upgrading the kernel package still causes its %post scriptlet to run. That scriptlet then does all the new-kernel-pkg stuff that causes the grub.conf to be modified. anaconda is doing its part by not running the bootloader upgrade steps, though.