I did a straight-through, all-defaults install of F16 Beta TC1, then took the generated /root/anaconda-ks.cfg , uncommented the partitioning lines, and uploaded it as:
then I tried an install from it, and got:
"The following error was found while parsing the kickstart configuration file:
The follow problem occurred on line 22 of the kickstart file:
Tried to use undefined partition pv.252003 in Volume Group specification"
Looks like we need to sort these lines using either device dependencies, or maybe the action sorting, depending on whether it is action-based or device-based.
Don't think dlehman's comment was meant to be private.
Proposing as a beta blocker, though this is a slight borderline case, under the new criterion:
"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"
borderline in that arguably 'as closely as possible' means 'using the generated anaconda-ks.cfg' without changes, but really, editing it and uncommenting the partition lines makes the kickstart *closer* to the default installation, in a way. We can debate it at the meeting, anyway.
Adam, you can try this:
It worked for me with a single-disk qemu install. What it does it make sure anaconda writes out the partitioning lines in anaconda-ks.cfg in a reasonable order.
Discussed at the 2011-09-09 blocker review meeting. We agreed this doesn't quite meet the definition of "duplicates the default interactive installation as closely as possible" because it's really to do with the auto-generation of kickstarts by anaconda; if you were to create a kickstart to duplicate a default install *from scratch* you wouldn't run into this. So we're taking it as NTH not blocker.
updates.img definitely produces better ordering, it gives:
only thing that worries me there is the /boot and biosboot partitions being after the LV - you'd think it'd be the other way around - but I'll test to see if that actually causes a problem.
well, the system installs and boots fine, so apparently it ain't a problem. confirming the fix, please commit!
anaconda-16.18-1.fc16 has been submitted as an update for Fedora 16.
* should fix your issue,
* was pushed to the Fedora 16 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing anaconda-16.18-1.fc16'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
Confirming this fix made it into RC1 and looks to be working well.
anaconda-16.18-1.fc16 has been pushed to the Fedora 16 stable repository. If problems still persist, please make note of it in this bug report.