Created attachment 751096 [details] Error message screenshot Description of problem: Trying to create another volume group when every other is full fails with "failed to create device" Version-Release number of selected component (if applicable): Anaconda usability test day livedvd. How reproducible: Always Steps to Reproduce: 1. Start graphical installation in virtual machine with four disks (8GB each) 2. Select all four disk for installation, manually edit partitions 3. Modify / mountpoint's Volume Group "fedora" and only select the first disk 3a. / mountpoint should now have 6.10 GB allocated 4. Try to add another mountpoint eg. /var Actual results: failed to create device Expected results: Anaconda ask to create another volume group on another disk Additional info: Workaround: move / mountpoint to another created volume group first and than create mountpoint
*** Bug 965817 has been marked as a duplicate of this bug. ***
I wrote a slightly more detailed explanation in the dupe, FWIW.
Please attach logs from /tmp/*log as individual text/plain files, especially storage.log
yeesh, it's perfectly obvious what's going on. I explained it in the dupe. But sure, let me jump through some hoops for you, it's not like I have anything else going on.
Note: if you try to create the new mount point with no specified size, there is no error, but the mount point is not created. If you specify any size at all, you get a red "Failed to add new device. Click for details." error bar, and clicking on pops up a dialog which simply says "failed to create device" with a Close button.
Created attachment 751450 [details] anaconda.log
Created attachment 751451 [details] program.log
Created attachment 751452 [details] storage.log
Created attachment 751454 [details] storage.state
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 19 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
This is still valid, exactly as per my reproduction steps in the dupe - https://bugzilla.redhat.com/show_bug.cgi?id=965817#c0 - in current Rawhide (2015-01-05).
Created attachment 978378 [details] storage.log from reproduction with 2015-01-05 Rawhide
Created attachment 978379 [details] program.log from reproduction with 2015-01-05 Rawhide
Created attachment 978380 [details] anaconda.log from reproduction with 2015-01-05 Rawhide
This bug appears to have been reported against 'rawhide' during the Fedora 22 development cycle. Changing version to '22'. More information and reason for this action is here: https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora22
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.