From Fedora Project Wiki
m (moved QA:Testcase Kickstart NfsServerPath KsCfg to QA:Testcase Kickstart Nfs Server Path Ks Cfg: divide words by _) |
(add a expected result to check install process runs unattended(ticket#217)) |
||
Line 7: | Line 7: | ||
|results= | |results= | ||
# The ks.cfg is successfully obtained from the specified location | # The ks.cfg is successfully obtained from the specified location | ||
# The install should proceed in accordance with the directives in the ks.cfg file | # The install should proceed in accordance with the directives in the {{filename|ks.cfg}} file | ||
# Anaconda should not prompt for user interaction if {{filename|ks.cfg}} is not specified | |||
}} | }} | ||
[[Category:Kickstart Delivery]] | [[Category:Kickstart Delivery]] |
Revision as of 10:11, 11 July 2011
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 enter the following at the boot prompt
linux ks=nfs:server:/path/ks.cfg
For example:linux ks=nfs:hank.test.redhat.com:/mnt/autotest/testmachines/505-lp1/testcase/ks.cfg
Expected Results
- The ks.cfg is successfully obtained from the specified location
- The install should proceed in accordance with the directives in the
ks.cfg
file - Anaconda should not prompt for user interaction if
ks.cfg
is not specified