Description of problem: I have done a default DVD installation. Then I took anaconda-ks.cfg and performed the same installation, but this time kickstarted. This should be a fully unattended installation. Instead, the main hub appeared with errors in the partitioning spoke. After clicking on details, I see: "Not enough free space on disks for automatic partitioning" The kickstart contains: # System bootloader configuration bootloader --location=mbr --boot-drive=vda autopart --type=plain # Partition clearing information clearpart --none --initlabel --drives=vda I also tried a different kickstart, which contains: # Wipe all disk zerombr bootloader --append="console=ttyS0" --timeout=1 clearpart --all --initlabel part biosboot --fstype=biosboot --size=1 part swap --fstype=swap --size=512 part / --fstype=ext4 --grow --size=1 That didn't work either. Version-Release number of selected component (if applicable): F18 Beta TC3 DVD anaconda 18.14 How reproducible: seems always Steps to Reproduce: 1. Take anaconda-ks.cfg from a default installation 2. Run kickstarted installation with it 3. Except unattended install, be surprised
Created attachment 625043 [details] anaconda-ks.cfg
Created attachment 625044 [details] anaconda.log
Created attachment 625045 [details] packaging.log
Created attachment 625046 [details] program.log
Created attachment 625047 [details] storage.log
Created attachment 625048 [details] syslog
Created attachment 625049 [details] X.log
Proposing as Beta blocker: " The installer must be able to successfully complete a scripted installation, using the installer's preferred scripting system, which duplicates the default interactive installation as closely as possible " https://fedoraproject.org/wiki/Fedora_18_Beta_Release_Criteria
Well, "clearpart --none --initlabel --drives=" isn't going to have any effect. According to the kickstart docs, --initlabel only means something if used with --all. But perhaps you've got enough free space so it doesn't really matter. However, there is definitely a kickstart-specific partitioning bug here that I can reproduce with your second test up there. Sending off a patch...
anaconda-18.15-1.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/anaconda-18.15-1.fc18
Package anaconda-18.15-1.fc18: * should fix your issue, * was pushed to the Fedora 18 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing anaconda-18.15-1.fc18' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-15903/anaconda-18.15-1.fc18 then log in and leave karma (feedback).
Discussed at 2012-10-11 blocker review meeting: http://meetbot.fedoraproject.org/fedora-qa/2012-10-11/f18beta-blocker-review-3.1.2012-10-11-16.04.log.txt . We agreed that it's slightly unclear what's going on here, but whatever it is, it seems pretty clearly a violation of "The installer must be able to successfully complete a scripted installation, using the installer's preferred scripting system, which duplicates the default interactive installation as closely as possible" , so it's accepted as a blocker. Chris, if you think we're off, please say so :)
With an updates.img made of the fix I'm no longer seeing problems with kickstart in graphical mode. I would consider this VERIFIED.
anaconda-18.16-1.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/anaconda-18.16-1.fc18
This is fixed in Beta TC4 (but due to bug 866449 the kickstarted installation still doesn't finish successfully).
anaconda-18.17-1.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/anaconda-18.17-1.fc18
Package anaconda-18.17-1.fc18: * should fix your issue, * was pushed to the Fedora 18 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing anaconda-18.17-1.fc18' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-16295/anaconda-18.17-1.fc18 then log in and leave karma (feedback).
Back to VERIFIED.
anaconda-18.18-1.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/anaconda-18.18-1.fc18
Package anaconda-18.18-1.fc18: * should fix your issue, * was pushed to the Fedora 18 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing anaconda-18.18-1.fc18' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-16402/anaconda-18.18-1.fc18 then log in and leave karma (feedback).
anaconda-18.19-1.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/anaconda-18.19-1.fc18
Package anaconda-18.19-1.fc18: * should fix your issue, * was pushed to the Fedora 18 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing anaconda-18.19-1.fc18' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-16528/anaconda-18.19-1.fc18 then log in and leave karma (feedback).
Fixed, anaconda stable, closing.