Hi! I noticed that some partitionning options of anaconda are located in the product.img file (Workstation vs Server product), that depends on the repo option given in the PXE boot. For example, the maxSize of the root partition set to 15Gigs for the server product is hardcoded in pyanaconda/installclass/fedora-server.py file from the product.img file and cannot be tweaked in the anaconda-ks.cfg file for another automated installation : both server and workstation installations will generate the same /root/anaconda-ks.cfg file, with the same "autopart --type=lvm" line, without any clue that one installation will use 15Gigs for / and another installation will take all free space. Maybe this option could be made available someway in an anaconda option, that would make the kickstart file self-contained ?
This affects server installs when using default guided partitioning and kickstarts it defaults to 15G. Proposing as a blocker for beta: "When using the guided partitioning flow, the installer must be able to: Complete an installation using any combination of disk configuration options it allows the user to select"
Discussed at 2016-10-03 blocker review meeting: [1]. This bug was rejected as Beta blocker: so far as we can determine there is not even a bug here, let alone a blocker. It is just the intended behaviour: if you specify autopart in your kickstart, the exact result will differ between Fedora flavors. [1] https://meetbot-raw.fedoraproject.org/fedora-blocker-review/2016-10-03/
Thanks for the feedback from the review meeting. It makes sense that flavour defaults are applied when autopart is selected.
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.