From Fedora Project Wiki
(adjust associated_release_criterion template invocation) |
No edit summary |
||
| Line 11: | Line 11: | ||
<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}} for the following information | ||
<pre> | <pre> | ||
INFO anaconda: Parsing kickstart: /run/install/ks.cfg | |||
</pre> | </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> 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. | <li> If sufficient kickstart commands are provided to fully automate an installation, the installer must not prompt for user input. | ||
Revision as of 13:54, 24 October 2014
Associated release criterion
This test case is associated with the Fedora_42_Beta_Release_Criteria#kickstart-delivery release criterion. If you are doing release validation testing, a failure of this test case may be a breach of that release criterion. If so, please file a bug and nominate it as blocking the appropriate milestone, using the blocker bug nomination page.
This test case is associated with the Fedora_42_Beta_Release_Criteria#kickstart-delivery release criterion. If you are doing release validation testing, a failure of this test case may be a breach of that release criterion. If so, please file a bug and nominate it as blocking the appropriate milestone, using the blocker bug nomination page.
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.cfgon 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.logfor the following informationINFO anaconda: Parsing kickstart: /run/install/ks.cfg
/run/install/ks.cfgshould contain your kickstart file - The installer should honor the kickstart commands provided in the
ks.cfgfile - If sufficient kickstart commands are provided to fully automate an installation, the installer must not prompt for user input.