The following was filed automatically by anaconda: anaconda 11.5.0.54 exception report Traceback (most recent call first): File "/usr/lib/anaconda/iw/partition_dialog_gui.py", line 218, in run usedev = self.storage.devicetree.getChildren(request)[0] File "/usr/lib/anaconda/iw/partition_gui.py", line 1119, in editPartition actions = parteditor.run() File "/usr/lib/anaconda/iw/partition_gui.py", line 1080, in editCB self.editPartition(device) IndexError: list index out of range
Created attachment 345199 [details] Attached traceback automatically from anaconda.
i was trying custom partitioning with all partitions encrypted. (except /boot) luks partitions were already there, i canceled all attempts to decrypt them.
even if i let it replace existing system install, it still crashes.
custom partitioning with f11 boot.iso from 22nd of may 2k9 doesn't like custom partitioning even if i started the install with an empty partition table. it enters a dropping master / setting master loop (as i see on c-a-f5). on c-a-f3 a see a INFO about formatting sda5, wich reminds me of an older bug from previous versions of fedora (10,9,8,...) however, the installer from the official f11 preview i386 gnome live cd worked on first attempt.
(In reply to comment #5) > custom partitioning with f11 boot.iso from 22nd of may 2k9 doesn't like custom > partitioning even if i started the install with an empty partition table. it > enters a dropping master / setting master loop (as i see on c-a-f5). > > on c-a-f3 a see a INFO about formatting sda5, it's actually "create format luks on /dev/sda5" wich reminds me of an older bug > from previous versions of fedora (10,9,8,...) > > however, the installer from the official f11 preview i386 gnome live cd worked > on first attempt. worth noting that form previous failed install attempt, the /home partition was not created before installing with the live cd.
_maybe_ f11preview live cd was able to install because of this bug? https://bugzilla.redhat.com/show_bug.cgi?id=501620 hmm, i was still asked to enter the password for existing luks partitions .... so maybe there's another reason
also, maybe some info here is related to other bugs, since it was collected during different install attempts.
Reproduced using the procedure described in comment#2 = Steps to reproduce = 1) Complete an install with encrypted partitions 2) Initiate an install again on this system 3) When prompted for passphrase to unlock existing encrypted volumes, click cancel 4) Select "Custom Partitioning" 5) Select a previous LVM PV and click "Edit" 6) Select 'format' and 'encrypt' and choose 'LVM' as the partition type, click "OK" This error does *not* occur if you either: * Enter the passphrase for the previous LUKS devices in step#3 * Or, if you remove the LVM PV and create a new LVM PV (instead of editing an existing) * Or, if you delete the volume group before editing the LVM PV This issue does not affect the default installation path and has a reasonable workaround. I'd like to propose removing this from the F11AnacondaBlocker list with a note on the Common_F11_bugs page detailing the workarounds.
This defect was discussed during the Fedora 11 Blocker bug review meeting. THe plan proposed in comment#9 was accepted. This issue will be documented in the F11 Common Bugs page and removed from the F11AnacondaBLocker list.
This defect has been added to the Common_F11_Bugs page. Please note here if the wording or proposed workaround needs any updates. https://fedoraproject.org/wiki/Common_F11_bugs#502310 Thanks, James
This bug appears to have been reported against 'rawhide' during the Fedora 11 development cycle. Changing version to '11'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
*** Bug 505136 has been marked as a duplicate of this bug. ***
Created attachment 348749 [details] Attached traceback automatically from anaconda.
*** Bug 505870 has been marked as a duplicate of this bug. ***
Fixed in anaconda-12.18-1.
anaconda-12.18-1 will show up where... F12 and RHEL6? Joshua
It will show up in rawhide within the next week, likewise in the F12 beta. Both F12 and RHEL6 will have a later version of anaconda.
as long as it makes it into those releases, I'm happy!
Retested on anaconda-12.32 (rawhide-20091001) using the procedure noted in comment#9. No longer seeing this failure. Moving to -> CLOSED RAWHIDE