right at the end of the install, I got this dialog all up in my face.. Traceback (most recent call first): File "/usr/lib/booty/bootloaderInfo.py", line 939, in grubbyDiskName return "hd%d" % self.drivelist.index(name) File "/usr/lib/booty/bootloaderInfo.py", line 900, in writeGrub f.write("(%s) /dev/%s\n" % (self.grubbyDiskName(drive), File "/usr/lib/booty/bootloaderInfo.py", line 1108, in write justConfig | (not self.useGrubVal)) File "/usr/lib/booty/bootloaderInfo.py", line 1216, in write chainList, defaultDev, justConfig, intf) File "/usr/lib/anaconda/bootloader.py", line 236, in writeBootloader justConfigFile, anaconda.intf) File "/usr/lib/anaconda/dispatch.py", line 208, in moveStep rc = stepFunc(self.anaconda) File "/usr/lib/anaconda/dispatch.py", line 131, in gotoNext self.moveStep() File "/usr/lib/anaconda/gui.py", line 1278, in nextClicked self.anaconda.dispatch.gotoNext() File "/usr/lib/anaconda/iw/progress_gui.py", line 80, in renderCallback self.intf.icw.nextClicked() File "/usr/lib/anaconda/gui.py", line 1299, in handleRenderCallback self.currentWindow.renderCallback() ValueError: list.index(x): x not in list
Created attachment 304562 [details] log
that machine has two disks. I told anaconda to ignore the 2nd one, as its bad.
Removing from F9 blocker, as we decided not to hold the release for this.
Changing version to '9' as part of upcoming Fedora 9 GA. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Does this happen with the final release of F9?