The following was filed automatically by anaconda: anaconda 15.28 exception report Traceback (most recent call first): File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/formats/__init__.py", line 419, in majorminor dev = udev_get_device(sysfs_path[4:]) File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/formats/__init__.py", line 270, in cacheMajorminor return self.majorminor # this does the caching File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/devices.py", line 700, in _preTeardown self.format.cacheMajorminor() File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/devices.py", line 714, in teardown if not self._preTeardown(recursive=recursive): File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/deviceaction.py", line 282, in __init__ device.teardown() File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/__init__.py", line 854, in destroyDevice action = ActionDestroyDevice(device) File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/partitioning.py", line 382, in clearPartitions storage.destroyDevice(leaf) File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/partitioning.py", line 189, in doAutoPartition clearPartitions(anaconda.storage) File "/usr/lib64/python2.7/site-packages/pyanaconda/dispatch.py", line 211, in moveStep rc = stepFunc(self.anaconda) File "/usr/lib64/python2.7/site-packages/pyanaconda/dispatch.py", line 130, in gotoNext self.moveStep() File "/usr/lib64/python2.7/site-packages/pyanaconda/gui.py", line 1257, in nextClicked self.anaconda.dispatch.gotoNext() TypeError: 'NoneType' object is not subscriptable
Created attachment 494672 [details] Attached traceback automatically from anaconda.
Reproduced by doing a default x86_64 installation on a KVM guest using a custom (anaconda-15.28-1) boot.iso image. The failure occurs after selecting which disks to partition, but prior to asking for confirmation before writing partition changes. I believe step=autopartitionexecute. This qualifies as a Final release blocker per the following criteria [1]: "The installer must be able to create and install to any workable partition layout using any file system offered in a default installer configuration, LVM, software, hardware or BIOS RAID, or combination of the above " [1] http://fedoraproject.org/wiki/Fedora_15_Final_Release_Criteria
Created attachment 494676 [details] Attached traceback automatically from anaconda.
Appears related to 1605b399f34ac923c457088d182da9db021191c8 (fixes another proposed F15 blocker bug#695389) ?
Discussed this issue with clumens, we both agreed that this issue looks like a clear blocker bug given the ease in reproducing and the stated criteria in comment#3. Adding whiteboard:AcceptedBlocker. 14:43:56 clumens: sounds like a blocker to me
Fixed by 05b092d450c806ed6968a1db9b84f71c33edbd67.
*** Bug 699254 has been marked as a duplicate of this bug. ***
anaconda-15.29-1.fc15 has been submitted as an update for Fedora 15. https://admin.fedoraproject.org/updates/anaconda-15.29-1.fc15
Package anaconda-15.29-1.fc15: * should fix your issue, * was pushed to the Fedora 15 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing anaconda-15.29-1.fc15' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/anaconda-15.29-1.fc15 then log in and leave karma (feedback).
VERIFIED fix using custom boot.iso
anaconda-15.29-1.fc15 has been pushed to the Fedora 15 stable repository. If problems still persist, please make note of it in this bug report.