Bug 648612 - AttributeError: 'x86BootloaderInfo' object has no attribute 'serial'
Summary: AttributeError: 'x86BootloaderInfo' object has no attribute 'serial'
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 13
Hardware: i386
OS: Linux
low
medium
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: anaconda_trace_hash:7642a4e88b8f30761...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-11-01 18:39 UTC by Paul Moore
Modified: 2010-11-02 21:18 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2010-11-02 21:18:16 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
Attached traceback automatically from anaconda. (258.60 KB, text/plain)
2010-11-01 18:39 UTC, Paul Moore
no flags Details

Description Paul Moore 2010-11-01 18:39:39 UTC
The following was filed automatically by anaconda:
anaconda 13.42 exception report
Traceback (most recent call first):
  File "/usr/lib/anaconda/booty/x86.py", line 282, in writeGrubConf
    if self.serial == 1:
  File "/usr/lib/anaconda/booty/x86.py", line 219, in writeGrub
    chainList, grubTarget, grubPath, cfPath)
  File "/usr/lib/anaconda/booty/x86.py", line 510, in write
    not self.useGrubVal)
  File "/usr/lib/anaconda/bootloader.py", line 217, in writeBootloader
    kernelList, otherList, defaultDev)
  File "/usr/lib/anaconda/dispatch.py", line 205, in moveStep
    rc = stepFunc(self.anaconda)
  File "/usr/lib/anaconda/dispatch.py", line 126, in gotoNext
    self.moveStep()
  File "/usr/lib/anaconda/text.py", line 659, in run
    anaconda.dispatch.gotoNext()
  File "/usr/bin/anaconda", line 1223, in <module>
    anaconda.intf.run(anaconda)
AttributeError: 'x86BootloaderInfo' object has no attribute 'serial'

Comment 1 Paul Moore 2010-11-01 18:39:43 UTC
Created attachment 456955 [details]
Attached traceback automatically from anaconda.

Comment 2 Brian Lane 2010-11-02 21:18:16 UTC
This was fixed as part of the cleanup for bug 589773


Note You need to log in before you can comment on or make changes to this bug.