Description of problem: When assigning partition to as disk with not enough free space error happens and custom partition interface becomes unusable. Version-Release number of selected component (if applicable): anaconda-20.25.14-1.fc20.x86_64 How reproducible: Always Steps to Reproduce: Prerequisites - two (virtual) disks of size 8.19GB 1. Start installation 2. Select both disks as installation destination 3. Use custom partitioning and standard partitions scheme 3. Auto-create partitions. It creates following scheme: vda1 /boot 500MB vdb1 / 8.19GB vda2 swap 1.63GB 4. Select / and press 'configure mount point', select disk with 6.05GB free 5. Press 'Update settings' Actual results: Error shown on bottom: device reconfiguration failed, click for details. Details: "not enough free space for disks". / becomes req0, swap becomes req2. Size of '/' partition changed to 1.024GB. Custom partition interface is not usable anymore - It is not possible to change / size or move it back. Only way out is refreshing disks and starting from scratch. Expected results: It moves disk and resizes it to max available space. (or says no free space and leaves everything as is at least) Additional info:
Created attachment 833930 [details] anaconda.log
Created attachment 833931 [details] ifcfg.log
Created attachment 833932 [details] program.log
Created attachment 833933 [details] storage.log
Blocker according to: The installer must be able to create and install to any workable partition layout using any file system and/or container format combination offered in a default installer configuration. (...Broadly what it's 'meant to mean' is that you should be able to do anything sane that the Installation Destination spoke attempts to let you do, without the installer exploding or failing...)
ah, I actually saw this one while I was trying to whack my problematic iSCSI target into shape: http://bugzilla.redhat.com/show_bug.cgi?id=1037934 . confirmed. kinda borderline for blocker as you can reset and try again, but it is busted indeed.
Discussed in 2013-12-09 Blocker Review meeting [1]. Voted as an AcceptedBlocker for violating the final criteria: "The installer must be able to create and install to any workable partition layout using any file system and/or container format combination offered in a default installer configuration." [2] [1] http://meetbot.fedoraproject.org/fedora-blocker-review/2013-12-09/ [2] http://fedoraproject.org/wiki/Fedora_20_Final_Release_Criteria#Disk_layouts
Probably related thing: When selecting regular partitions and encryption after doing auto-creation in custom partition it shows / on luks-req0 and swap on luks-req2.
anaconda-20.25.15-1.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/anaconda-20.25.15-1.fc20
I reproduced this with TC5, but not with RC1. Fixed.
anaconda-20.25.15-1.fc20, python-blivet-0.23.9-1.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.