Red Hat Bugzilla – Bug 588498
Backtrace in clearpart_gui when only uninitialized disks are found
Last modified: 2013-09-02 02:48:23 EDT
While attempting to work around bug#588493 (Unable to select local BIOS RAID drive as boot drive), I ran into this previously filed RHEL6 anaconda bug.
anaconda 13.39 exception report
Traceback (most recent call first):
File "/usr/lib/anaconda/iw/cleardisks_gui.py", line 146, in getScreen
self.bootDisk = sorted(names, self.anaconda.storage.compareDisks)
File "/usr/lib/anaconda/gui.py", line 1393, in setScreen
new_screen = self.currentWindow.getScreen(anaconda)
File "/usr/lib/anaconda/gui.py", line 1314, in nextClicked
IndexError: list index out of range
Local variables in innermost frame:
xml: <gtk.glade.XML object at 0x7fc0efb6fdc0 (PyGladeXML at 0x2cbdcc0)>
self: <ClearDisksWindow.ClearDisksWindow instance at 0x7fc10bc500e0>
anaconda: <__main__.Anaconda object at 0x7fc10441cf10>
See full traceback details in attachment#411109 [details]
This was a rather forward partitioning back/forward interaction. If the patch already fixed in RHEL6 is tested and isolated, I'd like to request pulling this into F13.
Ok, I'll cherry pick the fix into f13-branch.
This should be fixed in anaconda-13.40-1, moving to modified.
james, can you test with the updates.img? Thanks.
I'll try, but I suspect not, this involved hitting a previous bug, then going through a few iterations of hitting Back (and Next) a few times. I'll try to test tomorrow. If I'm not able to reproduce the original problem, we can move this along.
anaconda-13.40-1.fc13 has been submitted as an update for Fedora 13.
anaconda-13.40-1.fc13 has been pushed to the Fedora 13 testing repository. If problems still persist, please make note of it in this bug report.
If you want to test the update, you can install it with
su -c 'yum --enablerepo=updates-testing update anaconda'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/anaconda-13.40-1.fc13
I'm not able to reproduce this failure using anaconda-13.39-1 + an updates.img which includes the fix.
We should now be able to confirm that this bug is fixed using the images here:
if we have not yet confirmed the fix, can anyone able to reproduce this bug please test with one of those images and check that the bug is fixed? Thanks.
I'm not able to reproduce this failure using anaconda-13.40-1 from the URL in comment#8
okay, let's close it then.
Fedora Bugzappers volunteer triage team
anaconda-13.40-1.fc13 has been pushed to the Fedora 13 stable repository. If problems still persist, please make note of it in this bug report.