QA:Testcase Kickstart Http Server Ks Cfg

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.

Associated release criterion
This test case is associated with the Fedora_42_Beta_Release_Criteria#scripted-installation 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.

Associated release criterion
This test case is associated with the Fedora_42_Beta_Release_Criteria#unattended-installation 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 HTTP url. It requires a valid kickstart file and a working HTTP host.

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 a publicly-accessible place on your HTTP host.
3. Boot the system and add a inst.ks argument like the following to the boot command line:

   inst.ks=http://server.tld/path/to/your/ks.cfg

Prepared sample kickstart
You can use the following kickstart for a default installation from DVD. Please note that this will erase all your disks. The root password is 'fedora'.

http://mkrizek.fedorapeople.org/default.ks

Expected Results

1. The ks.cfg is successfully obtained from the specified location
2. The installer should honor the kickstart commands provided in the ks.cfg file
3. If sufficient commands are provided to fully automate an installation, the installer must not prompt for user input.