Description of problem:
1. Started with a previously successful 2-disk btrfs raid0 installation.
2. Chose both of those same disks for reinstallation.
3. Manual Partitioning, delete swap partition.
4. Dialog appears asking if I want to delete all other partitions in (group?) Unknown.
5. Confirmed this.
Version-Release number of selected component:
libreport version: 2.0.14
cmdline: /usr/bin/python /sbin/anaconda --liveinst --method=livecd:///dev/mapper/live-osimg-min --lang en_US.UTF-8
:The following was filed automatically by anaconda:
:anaconda 18.19 exception report
:Traceback (most recent call first):
: File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/spokes/custom.py", line 1670, in _destroy_device
: if device.type == "partition" and device.disk.format.exists:
: File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/spokes/custom.py", line 1699, in _destroy_device
: File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/spokes/custom.py", line 1760, in on_remove_clicked
:AttributeError: 'NoneType' object has no attribute 'format'
Created attachment 633091 [details]
Created attachment 633092 [details]
Created attachment 633093 [details]
Created attachment 633094 [details]
Created attachment 633095 [details]
Created attachment 633096 [details]
Created attachment 633097 [details]
Created attachment 633098 [details]
Created attachment 633099 [details]
Created attachment 633100 [details]
Created attachment 633101 [details]
Created attachment 633102 [details]
Created attachment 633103 [details]
Immediately preceding this bug, is Bug 869842, in which the installer has incorrectly determined there is enough free space for automatic partitioning. So I cloned this bug to make that one, and I'm cross referencing since it seems they may be related.
Propose as beta blocker, reason beta criterion 10: custom partitioning mode must be capable of destroying these partitions; and even if invalid the installer should not crash.
This is caused by the same underlying problem as bug 866101, but it reveals a missing check.
we're still fiddling with the criteria, but in general I'm broadly +1 to taking outright crashes for sane operations in custom part as blockers, so +1 blocker.
Discussed at 2012-10-29 QA meeting acting as a blocker review meeting: http://meetbot.fedoraproject.org/fedora-meeting/2012-10-29/fedora-qa.2012-10-29-15.00.html . We agreed that since this seems to impact only specific btrfs configurations it's not broad enough in impact to constitute a blocker. Note that the criteria for partitioning are still in revision so we didn't strictly consider the bug WRT the criteria. We felt the conditions needed to hit this bug are likely to be fairly rare and there are obvious workarounds (remove the partitions with some other tool).
it is accepted as NTH, though, as it may affect testability of the Beta.
Proposing as a Final blocker under the more generous Final partitioning criterion.
anaconda-18.22-1.fc18 has been submitted as an update for Fedora 18.
* should fix your issue,
* was pushed to the Fedora 18 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing anaconda-18.22-1.fc18'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
anaconda-18.23-1.fc18 has been submitted as an update for Fedora 18.
anaconda-18.24-1.fc18 has been submitted as an update for Fedora 18.
*** Bug 873332 has been marked as a duplicate of this bug. ***
anaconda-18.25-1.fc18 has been submitted as an update for Fedora 18.
anaconda-18.26-1.fc18 has been submitted as an update for Fedora 18.
18.26 went stable. Closing. (Bodhi closing of bugs when updates go stable is currently broken).