Bug 488636

Summary: selecting boot sector for bootloader causes exception
Product: [Fedora] Fedora Reporter: Charles R. Anderson <cra>
Component: anacondaAssignee: Anaconda Maintenance Team <anaconda-maint-list>
Status: CLOSED RAWHIDE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: medium    
Version: rawhideCC: anaconda-maint-list
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard: anaconda_trace_hash:be390a509c9522143cf89293d46a28d1fa1b4a2ef45d6bd08e22529abd2b4487
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-03-11 13:57:09 EDT Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
Attachments:
Description Flags
Attached traceback automatically from anaconda.
none
screenshot of bootloader device selection dialog none

Description Charles R. Anderson 2009-03-04 19:52:05 EST
The following was filed automatically by anaconda:
anaconda 11.5.0.23 exception report
Traceback (most recent call first):
  File "/usr/lib/booty/bootloaderInfo.py", line 2077, in getDiskPart
    cut = len(dev)
  File "/usr/lib/booty/bootloaderInfo.py", line 289, in setDevice
    (dev, part) = getDiskPart(device)
  File "/usr/lib/anaconda/iw/bootloader_main_gui.py", line 51, in getNext
    self.bl.setDevice(self.bldev)
  File "/usr/lib/anaconda/gui.py", line 1318, in nextClicked
    rc = self.currentWindow.getNext ()
AttributeError: PartitionDevice instance has no attribute '__len__'
Comment 1 Charles R. Anderson 2009-03-04 19:52:09 EST
Created attachment 334082 [details]
Attached traceback automatically from anaconda.
Comment 2 Charles R. Anderson 2009-03-04 20:00:08 EST
Created attachment 334083 [details]
screenshot of bootloader device selection dialog
Comment 3 Chris Lumens 2009-03-11 13:57:09 EDT
I just tried this and it is fixed for me.  Feel free to reopen this bug if you continue to see this problem.  Thanks for the bug report.