From Fedora Project Wiki

m (Added category)
m (fix numbering)
Line 6: Line 6:
== Steps To Reproduce ==
== Steps To Reproduce ==


 
# Prepare a valid kickstart file and copy to the server and path to be used for the test
1.  Prepare a valid kickstart file and copy to the 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>
 
1.  Boot the system and enter the following at the boot prompt
 
<code>linux ks=nfs:/server:/path/ks.cfg </code>
 


Example:
Example:
 
<pre>linux ks=nfs:hank.test.redhat.com:/mnt/autotest/testmachines/505-lp1/testcase/ks.cfg</pre>
<code>linux ks=nfs:hank.test.redhat.com:/mnt/autotest/testmachines/505-lp1/testcase/ks.cfg</code>




== Expected Results ==
== Expected Results ==


 
# The ks.cfg is successfully obtained from the specified location
1. The ks.cfg is successfully obtained from the specified location
# The install should proceed in accordance with the directives in the ks.cfg file
 
1. The install should proceed in accordance with the directives in the ks.cfg file


[[Category:Installer Test Cases|KickstartKsNfsServerPathKsCfg]]
[[Category:Installer Test Cases|KickstartKsNfsServerPathKsCfg]]

Revision as of 15:02, 16 July 2008

KickstartKsNfsServerPathKsCfg

Description

This test will verify that anaconda can download the requested kickstart file using a NFS uri. For further information on the ks= parameter, refer to 28.10. Starting a Kickstart Installation


Steps To Reproduce

  1. Prepare a valid kickstart file and copy to the server and path to be used for the test
  2. Boot the system and enter the following at the boot prompt
    linux ks=nfs:/server:/path/ks.cfg 

Example:

linux ks=nfs:hank.test.redhat.com:/mnt/autotest/testmachines/505-lp1/testcase/ks.cfg


Expected Results

  1. The ks.cfg is successfully obtained from the specified location
  2. The install should proceed in accordance with the directives in the ks.cfg file