Bug 865048

Summary: kickstarted install can't autopart disk
Product: [Fedora] Fedora Reporter: Kamil Páral <kparal>
Component: anacondaAssignee: Chris Lumens <clumens>
Status: CLOSED CURRENTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 18CC: awilliam, g.kaviyarasu, jonathan, robatino, vanmeeuwen+fedora
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: AcceptedBlocker
Fixed In Version: anaconda-18.15-1 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-10-23 13:05:44 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 752660    
Attachments:
Description Flags
anaconda-ks.cfg
none
anaconda.log
none
packaging.log
none
program.log
none
storage.log
none
syslog
none
X.log none

Description Kamil Páral 2012-10-10 17:05:54 UTC
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

Comment 1 Kamil Páral 2012-10-10 17:16:54 UTC
Created attachment 625043 [details]
anaconda-ks.cfg

Comment 2 Kamil Páral 2012-10-10 17:16:58 UTC
Created attachment 625044 [details]
anaconda.log

Comment 3 Kamil Páral 2012-10-10 17:17:01 UTC
Created attachment 625045 [details]
packaging.log

Comment 4 Kamil Páral 2012-10-10 17:17:24 UTC
Created attachment 625046 [details]
program.log

Comment 5 Kamil Páral 2012-10-10 17:19:15 UTC
Created attachment 625047 [details]
storage.log

Comment 6 Kamil Páral 2012-10-10 17:19:38 UTC
Created attachment 625048 [details]
syslog

Comment 7 Kamil Páral 2012-10-10 17:19:42 UTC
Created attachment 625049 [details]
X.log

Comment 8 Kamil Páral 2012-10-10 17:21:10 UTC
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

Comment 9 Chris Lumens 2012-10-10 18:18:17 UTC
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...

Comment 10 Fedora Update System 2012-10-11 01:04:51 UTC
anaconda-18.15-1.fc18 has been submitted as an update for Fedora 18.
https://admin.fedoraproject.org/updates/anaconda-18.15-1.fc18

Comment 11 Fedora Update System 2012-10-11 02:58:24 UTC
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).

Comment 12 Adam Williamson 2012-10-11 17:16:20 UTC
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 :)

Comment 13 Jesse Keating 2012-10-11 17:36:37 UTC
With an updates.img made of the fix I'm no longer seeing problems with kickstart in graphical mode.  I would consider this VERIFIED.

Comment 14 Fedora Update System 2012-10-12 01:06:40 UTC
anaconda-18.16-1.fc18 has been submitted as an update for Fedora 18.
https://admin.fedoraproject.org/updates/anaconda-18.16-1.fc18

Comment 15 Kamil Páral 2012-10-15 12:02:02 UTC
This is fixed in Beta TC4 (but due to bug 866449 the kickstarted installation still doesn't finish successfully).

Comment 16 Fedora Update System 2012-10-17 03:09:42 UTC
anaconda-18.17-1.fc18 has been submitted as an update for Fedora 18.
https://admin.fedoraproject.org/updates/anaconda-18.17-1.fc18

Comment 17 Fedora Update System 2012-10-17 17:31:25 UTC
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).

Comment 18 Adam Williamson 2012-10-18 00:09:34 UTC
Back to VERIFIED.

Comment 19 Fedora Update System 2012-10-18 02:38:32 UTC
anaconda-18.18-1.fc18 has been submitted as an update for Fedora 18.
https://admin.fedoraproject.org/updates/anaconda-18.18-1.fc18

Comment 20 Fedora Update System 2012-10-18 15:31:06 UTC
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).

Comment 21 Fedora Update System 2012-10-20 01:34:22 UTC
anaconda-18.19-1.fc18 has been submitted as an update for Fedora 18.
https://admin.fedoraproject.org/updates/anaconda-18.19-1.fc18

Comment 22 Fedora Update System 2012-10-20 03:52:27 UTC
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).

Comment 23 Kamil Páral 2012-10-23 13:05:44 UTC
Fixed, anaconda stable, closing.