From Fedora Project Wiki

m (Added category)
(link to an example kickstart, use setup section)
 
(14 intermediate revisions by 5 users not shown)
Line 1: Line 1:
= KickstartKsHdDevicePathKsCfg =
{{Template:Associated_release_criterion|Beta|kickstart-delivery}}
== Description ==
This test will verify that anaconda mounts and uses a ks.cfg located on the defined device.


{{QA/Test_Case
|description=This test will verify that anaconda mounts and uses a kickstart file located on a local block device.
|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 a partition for use with this test (e.g. on a USB key, or an existing partition on your hard drive). It should be a standard type partition.
|actions=
# Boot the system from the network install or DVD medium for the release under test and append the following to the boot prompt: <pre>inst.ks=hd:device:path/ks.cfg</pre> where <code>device</code> can be specified as <code>sdX</code> or <code>LABEL=label</code> or <code>UUID=uuid</code> (see more details at [https://rhinstaller.github.io/anaconda/boot-options.html#inst-repo inst.repo documentation]). For example, to load a kickstart file called {{filename|ks.cfg}} from a partition labeled <code>data</code>, append: <pre>inst.ks=hd:LABEL=data:/ks.cfg</pre>
|results=
# The system should boot from the chosen method and pause at the boot prompt
# The entry of <code>inst.ks=hd:device:path/ks.cfg </code> should be accepted without error
# The {{filename|ks.cfg}} file should be read from the specified device/path
# The installer should honor the kickstart commands provided in the {{filename|ks.cfg}} file
# If sufficient commands are provided to fully automate an installation, the installer must not prompt for user input.
}}


== Steps To Reproduce ==
[[Category:Kickstart Delivery]]
 
1.  Prepare a valid kickstart file and copy to the device and path to be used for the test (i.e. usb key).
 
1.  Boot the system and enter the following at the boot prompt
 
<code>linux ks=hd:device:path/ks.cfg </code>
 
 
Example:
 
<code>linux ks=hd:sda1:/mydir/ks.cfg</code>
 
 
== Expected Results ==
 
 
1. The system should boot from the chosen method and pause at the boot prompt
 
1. The entry of
<code>linux ks=hd:device:path/ks.cfg </code>
should be accepted without error
 
1. The ks.cfg file should be read from the specified device/path
 
1. The install should proceed in accordance with the directives in the ks.cfg file
 
[[Category:Installer Test Cases|KickstartKsHdDevicePathKsCfg]]

Latest revision as of 09:46, 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 mounts and uses a kickstart file located on a local block device.

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 a partition for use with this test (e.g. on a USB key, or an existing partition on your hard drive). It should be a standard type partition.

How to test

  1. Boot the system from the network install or DVD medium for the release under test and append the following to the boot prompt: 
    inst.ks=hd:device:path/ks.cfg
    where device can be specified as sdX or LABEL=label or UUID=uuid (see more details at inst.repo documentation). For example, to load a kickstart file called ks.cfg from a partition labeled data, append: 
    inst.ks=hd:LABEL=data:/ks.cfg

Expected Results

  1. The system should boot from the chosen method and pause at the boot prompt
  2. The entry of inst.ks=hd:device:path/ks.cfg should be accepted without error
  3. The ks.cfg file should be read from the specified device/path
  4. The installer should honor the kickstart commands provided in the ks.cfg file
  5. 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_Hd_Device_Path_Ks_Cfg&oldid=445923"