From Fedora Project Wiki
No edit summary |
No edit summary |
||
Line 9: | Line 9: | ||
|results= | |results= | ||
<ol> | <ol> | ||
<li> The kickstart file is successfully obtained from the specified location. This can be confirmed by the installer honoring the provided kickstart commands, or by inspecting the installer log file {{filename|anaconda.log}} for the following information | <li> The kickstart file is successfully obtained from the specified location. This can be confirmed by the installer honoring the provided kickstart commands, or by inspecting the installer log file {{filename|anaconda.log}} (/var/log/filename/anaconda.log) for the following information | ||
<pre> | <pre> | ||
INFO anaconda: Parsing kickstart: /run/install/ks.cfg | INFO anaconda: Parsing kickstart: /run/install/ks.cfg |
Revision as of 14:13, 10 December 2014
Description
This test will verify that anaconda can download the requested kickstart file using a NFS URL. For further information on the ks=parameter, refer to 28.10. Starting a Kickstart Installation
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 - Copy the kickstart file to the NFS server and path to be used for the test
- Boot the system and add the following argument to the boot prompt
inst.ks=nfs:server:/path/ks.cfg
Expected Results
- The kickstart file is successfully obtained from the specified location. This can be confirmed by the installer honoring the provided kickstart commands, or by inspecting the installer log file
anaconda.log
(/var/log/filename/anaconda.log) for the following informationINFO anaconda: Parsing kickstart: /run/install/ks.cfg
/run/install/ks.cfg
should contain your kickstart file - The installer should honor the kickstart commands provided in the
ks.cfg
file - If sufficient kickstart commands are provided to fully automate an installation, the installer must not prompt for user input.