From Fedora Project Wiki

(add a expected result to check install process runs unattended(ticket#217))
(Update expected results regarding kickstart install automation)
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 {{filename|ks.cfg}} file
# The installer should honor the kickstart commands provided in the {{filename|ks.cfg}} file
# Anaconda should not prompt for user interaction if {{filename|ks.cfg}} is not specified
# If sufficient 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 13:29, 26 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

  1. 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.
  2. Copy the kickstart file to a publicly-accessible place on your HTTP host.
  3. 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

  1. The ks.cfg is successfully obtained from the specified location
  2. The installer should honor the kickstart commands provided in the ks.cfg file
  3. If sufficient commands are provided to fully automate an installation, the installer must not prompt for user input.
Retrieved from "https://fedoraproject.org/w/index.php?title=QA:Testcase_Kickstart_Http_Server_Ks_Cfg&oldid=247158"