From Fedora Project Wiki

(add a expected result to check install process runs unattended(ticket#217))
(link to an example kickstart, use setup section)
 
(6 intermediate revisions by 5 users not shown)
Line 1: Line 1:
{{Template:Associated_release_criterion|Beta|kickstart-delivery}}
{{QA/Test_Case
{{QA/Test_Case
|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  [http://www.redhat.com/docs/manuals/enterprise/RHEL-5-manual/Installation_Guide-en-US/s1-kickstart2-startinginstall.html 28.10. Starting a Kickstart Installation]
|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  [http://www.redhat.com/docs/manuals/enterprise/RHEL-5-manual/Installation_Guide-en-US/s1-kickstart2-startinginstall.html 28.10. Starting a Kickstart Installation]
|setup=
# Prepare a valid kickstart file.
#* You can use an example kickstart available from [[QA:Testcase Kickstart Http Server Ks Cfg]].
#* If you want to create your own kickstart, you can 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 your NFS server
|actions=
|actions=
# 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]]
# Boot the system and add the following argument to the boot prompt <pre>inst.ks=nfs:server:/path/ks.cfg</pre>
# 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>
|results=
|results=
# The ks.cfg is successfully obtained from the specified location
<ol>
# The install should proceed in accordance with the directives in the {{filename|ks.cfg}} file
<li> 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 {{filename|anaconda.log}} (/var/log/filename/anaconda.log) for the following information
# Anaconda should not prompt for user interaction if {{filename|ks.cfg}} is not specified
<pre>
INFO anaconda: Parsing kickstart: /run/install/ks.cfg
</pre>
<code>/run/install/ks.cfg</code> should contain your kickstart file</li>
<li> The installer should honor the kickstart commands provided in the {{filename|ks.cfg}} file
<li> If sufficient kickstart commands are provided to fully automate an installation, the installer must not prompt for user input.
}}
}}




[[Category:Kickstart Delivery]]
[[Category:Kickstart Delivery]]

Latest revision as of 09:33, 6 May 2016

Associated release criterion
This test case is associated with the Fedora_42_Beta_Release_Criteria#kickstart-delivery release criterion. If you are doing release validation testing, a failure of this test case may be a breach of that release criterion. If so, please file a bug and nominate it as blocking the appropriate milestone, using the blocker bug nomination page.


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

Setup

  1. Prepare a valid kickstart file.
    • You can use an example kickstart available from QA:Testcase Kickstart Http Server Ks Cfg.
    • If you want to create your own kickstart, you can 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 your NFS server

How to test

  1. 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 (/var/log/filename/anaconda.log) for the following information 
    INFO anaconda: Parsing kickstart: /run/install/ks.cfg
    /run/install/ks.cfg should contain your kickstart file
  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.
Retrieved from "https://fedoraproject.org/w/index.php?title=QA:Testcase_Kickstart_Nfs_Server_Path_Ks_Cfg&oldid=445920"