Created attachment 1147780 [details] anaconda.log Description of problem: Doing a text mode kickstart install and the system simply shutdown after package selection. Adding nokill allowed me to see at the end of packaging.log: 21:40:40,339 ERR packaging: Installation failed: PayloadError('Not enough disk space to download the packages.',) Version-Release number of selected component (if applicable): 24.1-1 Expected results: System should display error message and wait for response.
Sorry, anaconda version is 24.13.3-1
Created attachment 1147799 [details] packaging.log I'll also note: 21:40:37,539 INFO packaging: 4030 packages selected totalling 18.02 GiB While it looks like the installed system was 15GB including the 3.8GB for /dnf.package.cache. Good to be conservative, but that seems a little excessive.
Hello Orion, yes the check is not perfect but we don't have all the information we need to get exact required space in the installation environment. This new space check is now based mostly on the rpm space check and limited knowledge of FS. But because we don't have all the information, we are using worst case scenario for both of these in the missing parts. In your use-case your base install is 15GB which means there is 17% of space left for your running system. Which is not so much from my point of view. If you think this amount of free space is too much for you, please fill another bug. Thank you for bug reporting, Jirka
Jirka - I've filed bug #1328151 for the disk requirements issue. Thanks.
Still seeing the system shutdown if there is not enough space with 25.20-1.
This message is a reminder that Fedora 24 is nearing its end of life. Approximately 2 (two) weeks from now Fedora will stop maintaining and issuing updates for Fedora 24. 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 '24'. 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 24 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 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 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.