Bug 501063

Summary: When upgrading, choosing 'skip bootloader' has no affect ... always installs new bootloader
Product: [Fedora] Fedora Reporter: James Laska <jlaska>
Component: anacondaAssignee: Anaconda Maintenance Team <anaconda-maint-list>
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 11CC: anaconda-maint-list, jturner, rmaximo, vanmeeuwen+fedora
Target Milestone: ---Keywords: CommonBugs, Reopened
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard: https://fedoraproject.org/wiki/Common_F11_bugs#501063
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-09-09 19:05:58 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description James Laska 2009-05-15 18:59:58 UTC 
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:
Comment 1 Chris Lumens 2009-05-18 15:54:29 UTC 

*** This bug has been marked as a duplicate of bug 494103 ***
Comment 2 James Laska 2009-05-27 14:29:40 UTC 
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.
Comment 3 James Laska 2009-06-09 12:06:29 UTC 
This issue has been documented at https://fedoraproject.org/wiki/Common_F11_bugs#501063
Comment 4 Bug Zapper 2009-06-09 15:54:43 UTC 
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
Comment 5 Chris Lumens 2009-09-09 19:05:58 UTC 
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.