From Fedora Project Wiki

m (Minor wiki cleanup)
(Converted to QA/Test_Case template, and provide sample kickstart)
Line 1: Line 1:
= Description =
{{QA/Test_Case
This test will verify that anaconda mounts and uses a ks.cfg located on the defined device.
|description=This test will verify that anaconda mounts and uses a ks.cfg located on a local blocker device.
 
|actions=
= Steps To Reproduce =
# 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 and copy to the device and path to be used for the test (i.e. usb key).
# Copy the kickstart file to block device for use with this test (e.g. a USB key).  For example, you may choose to copy the kickstart file to the {{filename|/boot}} directory which typically resides on the first partition of a disk.
# Boot the system and enter the following at the boot prompt <pre>linux ks=hd:device:path/ks.cfg </pre>.  For example, to load a kickstart file called ''/mydir/ks.cfg'' from the first partition on drive ''sda'', type: <pre>linux ks=hd:sda1:/mydir/ks.cfg</pre>
# Boot the system and enter the following at the boot prompt <pre>linux ks=hd:device:path/ks.cfg </pre>.  For example, to load a kickstart file called {{filename|ks.cfg}} from the first partition on drive ''sda'', type: <pre>linux ks=hd:sda1:/ks.cfg</pre>
 
|results=
= Expected Results =
# The system should boot from the chosen method and pause at the boot prompt
# The system should boot from the chosen method and pause at the boot prompt
# The entry of <pre>linux ks=hd:device:path/ks.cfg </pre> should be accepted without error
# The entry of <pre>linux ks=hd:device:path/ks.cfg </pre> should be accepted without error
# The ks.cfg file should be read from the specified device/path
# The ks.cfg file should be read from the specified device/path
# The install should proceed in accordance with the directives in the ks.cfg file
# The install should proceed in accordance with the directives in the ks.cfg file
}}


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

Revision as of 03:16, 9 November 2009

Description

This test will verify that anaconda mounts and uses a ks.cfg located on a local blocker device.


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 block device for use with this test (e.g. a USB key). For example, you may choose to copy the kickstart file to the /boot directory which typically resides on the first partition of a disk.
  3. Boot the system and enter the following at the boot prompt 
    linux ks=hd:device:path/ks.cfg
    . For example, to load a kickstart file called ks.cfg from the first partition on drive sda, type: 
    linux ks=hd:sda1:/ks.cfg

Expected Results

  1. The system should boot from the chosen method and pause at the boot prompt
  2. The entry of 
    linux 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 install should proceed in accordance with the directives in the ks.cfg file
Retrieved from "https://fedoraproject.org/w/index.php?title=QA:Testcase_Kickstart_Hd_Device_Path_Ks_Cfg&oldid=134978"