QA:Testcase Kickstart Nfs Server Path Ks Cfg

Associated release criterion
This test case is associated with the Fedora_40_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 can download the requested kickstart file using a NFS URL. For further information on the ks=parameter, refer to 28.10. Starting a Kickstart Installation

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 the NFS server and path to be used for the test
3. Boot the system and add the following argument to the boot prompt

   inst.ks=nfs:server:/path/ks.cfg

Expected Results

1. The kickstart file is successfully obtained from the specified location. This can be confirmed by the installer honoring the provided kickstart commands, or by inspecting the installer log file anaconda.log for the following information

   12:54:47,629 INFO loader: getting kickstart file
   12:54:47,658 INFO loader: doing kickstart... setting it up
   12:54:51,709 INFO loader: file location: nfs://<someserver>:/path/to/ks.cfg
   12:54:52,047 INFO loader: setting up kickstart
   12:54:52,437 INFO loader: kickstartFromUrl
   

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