From Fedora Project Wiki
(render the <pre> tag correctly) |
(drop the bug note, as it's fixed) |
||
(20 intermediate revisions by 4 users not shown) | |||
Line 1: | Line 1: | ||
{{Template:Associated_release_criterion|Beta|kickstart-delivery}} | |||
{{QA/Test_Case | {{QA/Test_Case | ||
|description= | |description= | ||
This test will verify that anaconda can load a kickstart file from a file:// path. This is a typical case for when the kickstart file is located in the initrd | This test will verify that anaconda can load a kickstart file from a {{filename|file://}} path. This is a typical case for when the kickstart file is located in the {{filename|initrd.img}}. | ||
|actions= | |actions= | ||
<ol> | |||
# Download the installer initial ramdisk. The ramdisk is typically called {{filename|images/pxeboot/initrd.img}} | <li> Prepare a valid kickstart file. For help creating a kickstart file, examine the file {{filename|/root/anaconda-ks.cfg}} on a previously installed system. This file contains the kickstart instructions used to install that system. For additional guidance on kickstart syntax, see [[Anaconda/Kickstart]] | ||
<li>Now you need to place your kickstart file inside the ramdisk. You can either do that manually, or use <code>--initrd-inject</code> option of {{package|python-virtinst}} tool, if you use it: | |||
<ul> | |||
<li>'''Option #1 - using a virt-install''': | |||
Use <code>--initrd-inject <kickstart></code> and <code>--extra-args "ks=file:/<kickstart>"</code> command line arguments. An example command would look like this (you need to change the ''location'' at least): | |||
{{#tag:pre|virt-install --name FedoraTest --ram 1024 --disk pool=default,size=10 --location http://dl.fedoraproject.org/pub/alt/stage/{{FedoraVersionNumber|next|short}}-Alpha-RC4/Fedora/x86_64/os/ --initrd-inject ks.cfg --extra-args "ks=file:/ks.cfg"}}</li> | |||
<li>'''Option #2 - modifying ramdisk manually''': | |||
<ol> | |||
<li> Download the installer initial ramdisk. The ramdisk is typically called {{filename|images/pxeboot/initrd.img}} | |||
<li> Place the kickstart file into the root directory of the installer initial ramdisk using the {{command|cpio}} command. <pre>echo ks.cfg | cpio -c -o >> initrd.img</pre> | |||
<li> Boot into the installer kernel ({{filename|vmlinuz}}) and the modified initial ramdisk ({{filename|initrd.img}}) using any available means (PXE, virt-install, virt-manager, etc) | |||
<li> At the bootloader prompt, provide a location for the kickstart file at the boot prompt. Using the example above: <pre>ks=file:///ks.cfg </pre> | |||
You also need to provide <code>[[Anaconda/Options#stage2|stage2=]]</code> boot option for Anaconda to start correctly. | |||
</ol> | |||
</ul> | |||
</li> | |||
</ol> | |||
|results= | |results= | ||
<ol> | <ol> | ||
<li> Confirm the ks.cfg is included in the initial ramdisk.</ | <li> Confirm the {{filename|ks.cfg}} is included in the initial ramdisk using <code>lsinitrd initrd.img {{!}} grep ks.cfg</code> command. | ||
<li> The installer successfully initiates a kickstart install in accordance with the instructions supplied by the {{filename|ks.cfg}} file included in the initial ramdisk. To ensure the kickstart file is properly loaded, inspect the {{filename|anaconda.log}} for a lines similar to the following: | |||
<pre> | |||
</ | 15:44:56,189 INFO loader: kernel command line: | ||
<li> The ks.cfg | 15:44:56,189 INFO loader: ks=file:///ks.cfg | ||
<li> | ... | ||
15:44:59,274 INFO loader: getting kickstart file | |||
15:44:59,274 INFO loader: setting up kickstart | |||
... | |||
15:44:59,906 INFO loader: doing kickstart... setting it up | |||
</pre> | |||
<li> The installer should honor the kickstart commands provided in the {{filename|ks.cfg}} file </li> | |||
<li> If sufficient commands are provided to fully automate an installation, the installer must not prompt for user input.</li> | |||
</ol> | </ol> | ||
}} | }} | ||
[[Category:Kickstart Delivery]] | [[Category:Kickstart Delivery]] |
Revision as of 05:05, 10 December 2013
Description
This test will verify that anaconda can load a kickstart file from a file://
path. This is a typical case for when the kickstart file is located in the initrd.img
.
How to test
- Prepare a valid kickstart file. For help creating a kickstart file, examine the file
/root/anaconda-ks.cfg
on a previously installed system. This file contains the kickstart instructions used to install that system. For additional guidance on kickstart syntax, see Anaconda/Kickstart - Now you need to place your kickstart file inside the ramdisk. You can either do that manually, or use
--initrd-inject
option ofpython-virtinst
tool, if you use it:- Option #1 - using a virt-install:
Use
--initrd-inject <kickstart>
and--extra-args "ks=file:/<kickstart>"
command line arguments. An example command would look like this (you need to change the location at least):virt-install --name FedoraTest --ram 1024 --disk pool=default,size=10 --location http://dl.fedoraproject.org/pub/alt/stage/41-Alpha-RC4/Fedora/x86_64/os/ --initrd-inject ks.cfg --extra-args "ks=file:/ks.cfg"
- Option #2 - modifying ramdisk manually:
- Download the installer initial ramdisk. The ramdisk is typically called
images/pxeboot/initrd.img
- Place the kickstart file into the root directory of the installer initial ramdisk using the
cpio
command.echo ks.cfg | cpio -c -o >> initrd.img
- Boot into the installer kernel (
vmlinuz
) and the modified initial ramdisk (initrd.img
) using any available means (PXE, virt-install, virt-manager, etc) - At the bootloader prompt, provide a location for the kickstart file at the boot prompt. Using the example above:
ks=file:///ks.cfg
You also need to provide
stage2=
boot option for Anaconda to start correctly.
- Download the installer initial ramdisk. The ramdisk is typically called
- Option #1 - using a virt-install:
Use
Expected Results
- Confirm the
ks.cfg
is included in the initial ramdisk usinglsinitrd initrd.img | grep ks.cfg
command. - The installer successfully initiates a kickstart install in accordance with the instructions supplied by the
ks.cfg
file included in the initial ramdisk. To ensure the kickstart file is properly loaded, inspect theanaconda.log
for a lines similar to the following:15:44:56,189 INFO loader: kernel command line: 15:44:56,189 INFO loader: ks=file:///ks.cfg ... 15:44:59,274 INFO loader: getting kickstart file 15:44:59,274 INFO loader: setting up kickstart ... 15:44:59,906 INFO loader: doing kickstart... setting it up
- The installer should honor the kickstart commands provided in the
ks.cfg
file - If sufficient commands are provided to fully automate an installation, the installer must not prompt for user input.