Bug 590823

Summary: Text-mode upgrade fails when installing new bootloader -- KeyError: 'bootloader'
Product: [Fedora] Fedora Reporter: James Laska <jlaska>
Component: anacondaAssignee: Anaconda Maintenance Team <anaconda-maint-list>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 13CC: anaconda-maint-list, jonathan, jturner, vanmeeuwen+fedora
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-05-10 20:00:55 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:
Bug Depends On:    
Bug Blocks: 507681    

Description James Laska 2010-05-10 18:48:47 UTC
Description of problem:

Doing a Fedora 13 text-mode upgrade, and selecting to create a New bootloader configuration results in ...

anaconda 13.41 exception report
Traceback (most recent call first):
  File "/usr/lib/anaconda/text.py", line 597, in run
    (file, classNames) = stepToClasses[step]
  File "/usr/bin/anaconda", line 1223, in <module>
    anaconda.intf.run(anaconda)
KeyError: 'bootloader'

Version-Release number of selected component (if applicable):
 * anaconda-13.41-1

How reproducible:
 * 100%

Steps to Reproduce:
1. Install Fedora 12
2. Start a text-mode install of Fedora 13
3. Choose to upgrade existing system
4. Select to create a new bootloader configuration
  
Actual results:


anaconda 13.41 exception report
Traceback (most recent call first):
  File "/usr/lib/anaconda/text.py", line 597, in run
    (file, classNames) = stepToClasses[step]
  File "/usr/bin/anaconda", line 1223, in <module>
    anaconda.intf.run(anaconda)
KeyError: 'bootloader'

Expected results:

No traceback

Additional info:

 * see full traceback as attachment#412924 [details]

Comment 1 James Laska 2010-05-10 19:03:27 UTC
== Acceptable workarounds for this bug ==

 1. Do a graphical or VNC upgrade
 2. Choose to skip or update the existing bootloader configuration (anything but create a new one).

Comment 2 Chris Lumens 2010-05-10 20:00:55 UTC

*** This bug has been marked as a duplicate of bug 580378 ***