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 ks.cfg located on a local block device.

How to test

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.
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.
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 
```
. For example, to load a kickstart file called ks.cfg from the first partition on drive sda, append:
```
inst.ks=hd:sda1:/ks.cfg
```

The system should boot from the chosen method and pause at the boot prompt
The entry of
```
inst.ks=hd:device:path/ks.cfg 
```
should be accepted without error
The ks.cfg file should be read from the specified device/path
The installer should honor the kickstart commands provided in the ks.cfg file
If sufficient commands are provided to fully automate an installation, the installer must not prompt for user input.