From Fedora Project Wiki
(add a expected result to check install process runs unattended(ticket#217)) |
No edit summary |
||
(5 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=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 [http://www.redhat.com/docs/manuals/enterprise/RHEL-5-manual/Installation_Guide-en-US/s1-kickstart2-startinginstall.html 28.10. Starting a Kickstart Installation] | |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 [http://www.redhat.com/docs/manuals/enterprise/RHEL-5-manual/Installation_Guide-en-US/s1-kickstart2-startinginstall.html 28.10. Starting a Kickstart Installation] | ||
Line 4: | Line 6: | ||
# 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]] | # 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]] | ||
# Copy the kickstart file to the NFS server and path to be used for the test | # Copy the kickstart file to the NFS server and path to be used for the test | ||
# Boot the system and | # Boot the system and add the following argument to the boot prompt <pre>inst.ks=nfs:server:/path/ks.cfg</pre> | ||
|results= | |results= | ||
<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}} (/var/log/filename/anaconda.log) for the following information | |||
<pre> | |||
INFO anaconda: Parsing kickstart: /run/install/ks.cfg | |||
</pre> | |||
<code>/run/install/ks.cfg</code> should contain your kickstart file</li> | |||
<li> The installer should honor the kickstart commands provided in the {{filename|ks.cfg}} file | |||
<li> If sufficient kickstart commands are provided to fully automate an installation, the installer must not prompt for user input. | |||
}} | }} | ||
[[Category:Kickstart Delivery]] | [[Category:Kickstart Delivery]] |
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.