Bug 868702
| Summary: | AttributeError: 'MountpointSelector' object has no attribute '_root' | ||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Reartes Guillermo <rtguille> | ||||||||||||||||||||||||||||||||
| Component: | anaconda | Assignee: | Chris Lumens <clumens> | ||||||||||||||||||||||||||||||||
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||||||||||||||||||||||||
| Severity: | unspecified | Docs Contact: | |||||||||||||||||||||||||||||||||
| Priority: | unspecified | ||||||||||||||||||||||||||||||||||
| Version: | 18 | CC: | awilliam, g.kaviyarasu, jonathan, public.oss, vanmeeuwen+fedora | ||||||||||||||||||||||||||||||||
| Target Milestone: | --- | ||||||||||||||||||||||||||||||||||
| Target Release: | --- | ||||||||||||||||||||||||||||||||||
| Hardware: | x86_64 | ||||||||||||||||||||||||||||||||||
| OS: | Unspecified | ||||||||||||||||||||||||||||||||||
| Whiteboard: | abrt_hash:7d1ce6340a19e9a7ef6c32a14007433d398219afcb8c4ffb8538a2af0df16ecc | ||||||||||||||||||||||||||||||||||
| Fixed In Version: | anaconda-18.20-1 | Doc Type: | Bug Fix | ||||||||||||||||||||||||||||||||
| Doc Text: | Story Points: | --- | |||||||||||||||||||||||||||||||||
| Clone Of: | Environment: | ||||||||||||||||||||||||||||||||||
| Last Closed: | 2012-11-23 05:22:53 UTC | Type: | --- | ||||||||||||||||||||||||||||||||
| Regression: | --- | Mount Type: | --- | ||||||||||||||||||||||||||||||||
| Documentation: | --- | CRM: | |||||||||||||||||||||||||||||||||
| Verified Versions: | Category: | --- | |||||||||||||||||||||||||||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||||||||||||||||||||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||||||||||||||||||||||||||
| Embargoed: | |||||||||||||||||||||||||||||||||||
| Attachments: |
|
||||||||||||||||||||||||||||||||||
|
Description
Reartes Guillermo
2012-10-21 20:48:07 UTC
Created attachment 631064 [details]
File: anaconda-tb
Created attachment 631065 [details]
File: product
Created attachment 631067 [details]
File: type
Created attachment 631069 [details]
File: ifcfg.log
Created attachment 631070 [details]
File: storage.log
Created attachment 631071 [details]
File: version
Created attachment 631072 [details]
File: environ
Created attachment 631073 [details]
File: anaconda.log
Created attachment 631074 [details]
File: syslog
Created attachment 631075 [details]
File: hashmarkername
Created attachment 631076 [details]
File: packaging.log
Created attachment 631077 [details]
File: cmdline_file
Created attachment 631078 [details]
File: release
Created attachment 631079 [details]
File: program.log
Anaconda custom partitioning, removing one of two volume swaps, from the F18 list.
Existing partition layout includes volumes for two distro installations (and more) :
. sda1 ext2 (neutral loader)
- sda3 lvm {boot1, boot2, ...}
- sda5 lvm+luks {root1, root2, swap1, swap2, ..., data}
Anaconda permits to unlock the crypt fine, then assign the desired mount points to F18 installation : one of the boot volumes, one of the root volumes. As per the swaps, both were automatically added to F18 partition layout proposal.
1. Select one of the swaps
2. Hit the "-" button at the list bottom
This leads to this crash.
Package: anaconda-18.19-1.fc18.x86_64
OS Release: Fedora release 18
Does updates=http://clumens.fedorapeople.org/868702.img fix this for you? I reproduced several times with these steps: 0. Booting a guest with preexisting partitions. 1. Enter STORAGE: INSTALLATION DESTINATION, select the first disk. 2. Press continue and select MANUAL PARTITIONING. 3. Expand the 'UNKNOWN' tree. Select a partition (RAID in this example) 4. Expand 'Customize' Tree, check 'encrypt' & press 'apply' This causes the selected partition entry to be relocated in the 'New Fedora' tree. Please note that the 'Software RAID' and other stuff is still shown. These should not be shown, since there is nothing selected at the moment. 5. Expand the 'New Fedora...' Tree. Software RAID will be selected. That is abnormal, because only items in an expanded Tree can be selected. Most likely when it was relocated the 'UNKNOWN' tree should have been collapsed and the 'New Fedora' tree should have been expanded, keeping the item selected. 7. By just removing '-' the partition, then the error pop-pups. Clearly, i could not reproduce it with previous comment methods. I tested the updates image from previous comment and with these steps i could no longer reproduce the issue. I tried a couple of times, just to be sure. Additional Info: When i perform steps 3 & 4, i failed to notice that when i expand the 'New Fedora...' Tree there is a BIOS Boot entry which i did not put there, it just appears. And when booting with the updates image, when removing the partition, it also removes that 'ghost' BIOS Boot entry too. Existing Partitions on the selected disk: GPT 1 Bios Boot (EF02) 1mb 2 STANDARD PARTITION (0700) 4.9gb 3 STANDARD PARTITION (0700) 500mb 4 RAID PARTITION (FD00) 2gb 5 STANDARD PARTITION (0700) 1.9gb Okay, I'll post the patch later. Got some other stuff to sort out first. Created attachment 631773 [details] Anaconda log without, then with updates image from comment #16 Thanks, I tested your image too : - Crash is no longer reproduceable with the updates However - Second swap is still not removeable from F18 layout - Is the previously selected / volume, removed instead ? That's a very unexpected behaviour: I had assigned / and /boot, hit Apply Changes, went to F18 section and tried to remove of of the swaps. Root was surely still showing up in the GUI. That's only when I hit "Finish Partioning" that, surprisingly, Anaconda main screen did show the section unsatisfied. As we an see in anaconda.log, it states no / part was selected... Indeed, while entering custom partitioning again, / partition was no longer listed in F18 section. I assigned it again and, this time, it took it into consideration. 100% reproduceable (and reproduced at least 3 times). Hopes the log helps. Please open a separate bug for the separate issue. Thanks. This bug looks to have been fixed for many anaconda builds now but missed being closed. If you find you are still experiencing it with Fedora 18 Beta (RC1) or later, please re-open the bug. (ref comment #19) |