From Fedora Project Wiki

m (Minor wiki cleanup)
m (Use wiki template)
Line 1: Line 1:
= Description =
{{QA/Test_Case
|description=
This test will verify that anaconda can load a kickstart file from a file:// path.  This is a typical case for when the kickstart file is located in the initrd or stage#1 environment.
This test will verify that anaconda can load a kickstart file from a file:// path.  This is a typical case for when the kickstart file is located in the initrd or stage#1 environment.
 
|actions=
= Steps To Reproduce =
# Prepare a valid kickstart file (for guidance, see [[Anaconda/Kickstart]]).
# Prepare a valid kickstart file and copy to a on disk location accessible by the stage#1 loaderThis is typically copied inside the initrd used for the installation.
# Download the installer initial ramdiskThe ramdisk is typically called {{filename|images/pxeboot/initrd.img}}.
# Boot the system and enter the following at the boot prompt <pre>linux ks=file://path/ks.cfg </pre>
# Place the kickstart file into the root directory of the installer initial ramdisk using the {{command|pax}} command.  For example,
 
## Untar the ramdisk: <pre>zcat initrd.img > initrd.cpio</pre>
Example:
## Add the kickstart file: <pre>pax -w -a -f initrd.cpio ks.cfg</pre>
<pre>linux ks=file:/etc/ks.cfg</pre>
## Compress the image: <pre>gzip -c initrd.cpio > initrd.img</pre>
 
# Boot into the installer using any available means
= Expected Results =
# At the bootloader prompt, provide a location for the kickstart file at the boot prompt.  Using the example above: <pre>linux ks=file:///ks.cfg </pre>
|results=
# Confirm the ks.cfg is included in the initial ramdisk. 
#: <pre>zcat /boot/initrd.img | pax | grep ks.cfg
#: ks.cfg </pre>
# The ks.cfg is successfully obtained from the specified location
# The ks.cfg is successfully obtained from the specified location
# 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 15:58, 6 November 2009

Description

This test will verify that anaconda can load a kickstart file from a file:// path. This is a typical case for when the kickstart file is located in the initrd or stage#1 environment.


How to test

  1. Prepare a valid kickstart file (for guidance, see Anaconda/Kickstart).
  2. Download the installer initial ramdisk. The ramdisk is typically called images/pxeboot/initrd.img.
  3. Place the kickstart file into the root directory of the installer initial ramdisk using the pax command. For example,
    1. Untar the ramdisk:
      zcat initrd.img > initrd.cpio
    2. Add the kickstart file:
      pax -w -a -f initrd.cpio ks.cfg
    3. Compress the image:
      gzip -c initrd.cpio > initrd.img
  4. Boot into the installer using any available means
  5. At the bootloader prompt, provide a location for the kickstart file at the boot prompt. Using the example above:
    linux ks=file:///ks.cfg 

Expected Results

  1. Confirm the ks.cfg is included in the initial ramdisk.
    zcat /boot/initrd.img | pax | grep ks.cfg
    ks.cfg
  2. The ks.cfg is successfully obtained from the specified location
  3. The install should proceed in accordance with the directives in the ks.cfg file