From Fedora Project Wiki
m (moved QA:Testcase Kickstart HttpServer KsCfg to QA:Testcase Kickstart Http Server Ks Cfg: divide words by _) |
(add a expected result to check install process runs unattended(ticket#217)) |
||
Line 8: | Line 8: | ||
|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 HTTP url. It requires a valid kickstart file and a working HTTP host.
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 a publicly-accessible place on your HTTP host.
- Boot the system and add a
ks
argument like the following to the boot command line:ks=http://server.tld/path/to/your/ks.cfg
An example of a kickstart file is:http://rhe.fedorapeople.org/install/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