Created attachment 1090396 [details] anaconda.log Description of problem: Kickstart installation fails with the message "Not enough space in file systems for the current software selection. An additional 2.79 GiB is needed." How reproducible: 100% Steps to Reproduce: 1. Kickstart with the following storage configuration(this worked on Fedora 22): bootloader --location=mbr --boot-drive=sda clearpart --all --initlabel --drives=sda part /boot --fstype="ext4" --ondisk=sda --size=512 part pv.3384 --size=1 --ondisk=sda --grow --encrypted --passphrase=test01 volgroup odin --pesize=4096 pv.3384 logvol /var --fstype="xfs" --size=10240 --name=var --vgname=odin logvol / --fstype="xfs" --size=1024 --name=root --vgname=odin logvol swap --fstype="xfs" --size=4096 --name=swap --vgname=odin logvol /usr --fstype="xfs" --size=10240 --name=usr --vgname=odin logvol /home --fstype="xfs" --size=51200 --name=home --vgname=odin logvol /var/lib/libvirt/images --fstype="xfs" --size=51200 --name=vms --vgname=odin Actual results: Installation halts. Expected results: Installation should carry on. Additional info: The same configuration without encrypted volume works. bootloader --location=mbr --boot-drive=sda clearpart --all --initlabel --drives=sda part /boot --fstype="ext4" --ondisk=sda --size=512 part pv.3384 --size=1 --ondisk=sda --grow volgroup odin --pesize=4096 pv.3384 logvol /var --fstype="xfs" --size=10240 --name=var --vgname=odin logvol / --fstype="xfs" --size=1024 --name=root --vgname=odin logvol swap --fstype="xfs" --size=4096 --name=swap --vgname=odin logvol /usr --fstype="xfs" --size=10240 --name=usr --vgname=odin logvol /home --fstype="xfs" --size=51200 --name=home --vgname=odin logvol /var/lib/libvirt/images --fstype="xfs" --size=51200 --name=vms --vgname=odin
Created attachment 1090397 [details] storage.log
Created attachment 1090398 [details] program.log
Hello Johan, could you please provide me these infomramations? Was that Server, Workstation and did you have special packages selection if yes which packages? Was that fully automatic kickstart installation? Please attach packaging.log which you can find in /tmp/packaging.log? Thank you, Jirka Konecny
(In reply to Jiri Konecny from comment #3) > Hello Johan, > > could you please provide me these infomramations? > Was that Server, Workstation and did you have special packages selection if > yes which packages? Server, I'm uploading the entire kickstart file for reference. > Was that fully automatic kickstart installation? Yes > Please attach packaging.log which you can find in /tmp/packaging.log? I can provide this later this evening as I don't have access to it right now.
Created attachment 1090608 [details] kickstart file used when issue occurs
Created attachment 1090784 [details] packaging.log
From anaconda.log: 21:32:23,055 ERR anaconda: storage configuration failed: device is too small for new format 21:32:26,304 INFO anaconda: fs space: 0 B needed: 2.79 GiB So this seems as problem in blivet when the device isn't created and you then try to install to nothing (0 B). The error message is really bad I will look on this and try to give there a meaningful warning.
Workaround possible by setting the size to something larger and setting a fstype. For example: part pv.3384 --fstype="lvmpv" --size=80000 --ondisk=sda --grow --encrypted --passphrase=test01 Full example: bootloader --location=mbr --boot-drive=sda clearpart --all --initlabel --drives=sda part /boot --fstype="ext4" --ondisk=sda --size=512 part pv.3384 --fstype="lvmpv" --size=80000 --ondisk=sda --grow --encrypted --passphrase=test01 volgroup odin --pesize=4096 pv.3384 logvol /var --fstype="xfs" --size=10240 --name=var --vgname=odin logvol / --fstype="xfs" --size=1024 --name=root --vgname=odin logvol swap --fstype="xfs" --size=4096 --name=swap --vgname=odin logvol /usr --fstype="xfs" --size=10240 --name=usr --vgname=odin logvol /home --fstype="xfs" --size=51200 --name=home --vgname=odin logvol /var/lib/libvirt/images --fstype="xfs" --size=51200 --name=vms --vgname=odin
This message is a reminder that Fedora 23 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 23. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '23'. 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 23 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.
Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 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.