Hide Forgot
libreport version: 2.0.6 executable: /usr/bin/python hashmarkername: anaconda kernel: 3.1.0-5.fc16.x86_64 product: Fedora reason: AttributeError: 'NoneType' object has no attribute 'type' time: Tue Nov 1 15:19:55 2011 version: 16 anaconda-tb-6TrRZ0: Binary file, 521495 bytes description: :The following was filed automatically by anaconda: :anaconda 16.24 exception report :Traceback (most recent call first): : File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/__init__.py", line 395, in doIt : if boot.type == "mdarray": : File "/usr/lib64/python2.7/site-packages/pyanaconda/packages.py", line 122, in turnOnFilesystems : anaconda.storage.doIt() : File "/usr/lib64/python2.7/site-packages/pyanaconda/dispatch.py", line 373, in dispatch : self.dir = self.steps[self.step].target(self.anaconda) : File "/usr/lib64/python2.7/site-packages/pyanaconda/dispatch.py", line 241, in go_forward : self.dispatch() : File "/usr/lib64/python2.7/site-packages/pyanaconda/gui.py", line 1201, in nextClicked : self.anaconda.dispatch.go_forward() :AttributeError: 'NoneType' object has no attribute 'type'
Created attachment 531187 [details] File: anaconda-tb-6TrRZ0
This is what I did: 1. Install Fedora-14-x86_64-Live-Desktop.iso 2. Enable updates-testing 3. yum update 4. yum install livecd-tools 5. livecd-iso-to-disk --efi --format --reset-mbr Fedora-16-x86_64-netinst.iso /dev/sdX 6. Boot via EFI on Lenovo ThinkPad T520 7. Edit boot menu entry to add "askmethod" 8. Choose URL method with http:// URL to a loopback mounted copy of Fedora-16-x86_64-DVD.iso (RC3) 9. Select Upgrade an Existing Installation and choose the Fedora 14 install There was also an existing Fedora 16 install on another disk that I gave the LUKS password to, but did not choose to upgrade.
Also reproducible without giving LUKS password to other F16 install. So the layout of the unrelated F16 VG doesn't affect this bug.
This bug only happens when booting F16 in EFI mode. If using legacy BIOS boot, F16 upgrade proceeds normally without hitting this bug.
I'm assuming this bug happens because the original install was a MBR partition table installed in Lagacy/non-EFI mode, but the upgrade was attempted in EFI mode. I can't think of a reason why one would want to do that, but perhaps the installer should complain about attempted cross-grades MBR-->EFI instead of crashing.
Same problem for me. I don't think it's a MBR related issue. I have a native EFI installation and F16's anaconda used to work fine, both in upgrade and in fresh, scratch install. Now i tried the upgrade to F17 and anaconda crashes.
With the move to fedup for F18, anaconda is now completely out of the upgrade game. That tool does not use anaconda at all so you shouldn't be hitting this problem.