QA:Testcase Kickstart Nfs Server Path Ks Cfg

From FedoraProject

(Difference between revisions)
Jump to: navigation, search
(Update kickstart install automation expected result)
(inst.ks)
Line 4: Line 4:
 
# 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 enter the following at the boot prompt <pre>linux ks=nfs:server:/path/ks.cfg </pre> For example:<pre>linux ks=nfs:hank.test.redhat.com:/mnt/autotest/testmachines/505-lp1/testcase/ks.cfg</pre>
+
# Boot the system and add the following argument to the boot prompt <pre>inst.ks=nfs:server:/path/ks.cfg</pre>
 
|results=
 
|results=
 
<ol>
 
<ol>

Revision as of 15:55, 25 June 2013

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

  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 the NFS server and path to be used for the test
  3. Boot the system and add the following argument to the boot prompt
    inst.ks=nfs:server:/path/ks.cfg

Expected Results

  1. 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 for the following information
    12:54:47,629 INFO loader: getting kickstart file
    12:54:47,658 INFO loader: doing kickstart... setting it up
    12:54:51,709 INFO loader: file location: nfs://<someserver>:/path/to/ks.cfg
    12:54:52,047 INFO loader: setting up kickstart
    12:54:52,437 INFO loader: kickstartFromUrl
    
  2. The installer should honor the kickstart commands provided in the ks.cfg file
  3. If sufficient kickstart commands are provided to fully automate an installation, the installer must not prompt for user input.