| Summary: | AttributeError: 'NoneType' object has no attribute 'type' | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Charles R. Anderson <cra> | ||||
| Component: | anaconda | Assignee: | Anaconda Maintenance Team <anaconda-maint-list> | ||||
| Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 16 | CC: | anaconda-maint-list, candeliere, jonathan, muglikar, tcpip4000, vanmeeuwen+fedora | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | x86_64 | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | abrt_hash:6bf46d2e60544ef24948886ee025f920fa75f9c4c12afb92cb7c60aaedc00a10 | ||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2012-12-18 04:37:41 UTC | Type: | --- | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Attachments: |
|
||||||
|
Description
Charles R. Anderson
2011-11-01 19:20:35 UTC
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. |