QA:Testcase install repository HTTP variation

Associated release criterion
This test case is associated with the Basic_Release_Criteria#remote-package-sources 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 is to verify that Anaconda's inst.repo boot option works together with an HTTP/HTTPS repository.

Setup

1. Prepare any non-live media for booting the installer (anything except Live.iso).
2. Pick a mirror URL from the list of available mirrors. For example here's a list of Fedora 42 x86_64 mirrors. The top ones should be closest to you (and possibly fastest).
   • Make sure the repository architecture matches the architecture of your installer media.
   • You can also use your own install repository, if you have one.

How to test

1. Before booting the installer, specify a target HTTP/HTTPS repository (selected in previous step) by adding a following boot option:

   inst.repo=URL

   • If proxy is needed, add it as another option:

     proxy=[protocol://][username[:password]@]host[:port]

   • Example:

     inst.repo=https://mirrors.kernel.org/fedora/development/42/x86_64/os/ 

2. Proceed with installation.

Expected Results

1. The installer auto-selects requested HTTP/HTTPS repository as the installation source in its GUI
2. The requested repository is used to download and install required packages. This can be checked by inspecting /tmp/packaging.log. Example output:

   09:34:37,295 DEBUG packaging: adding yum repo anaconda with baseurl https://mirrors.kernel.org/fedora/development/42/x86_64/os/ and mirrorlist None
   09:34:37,313 DEBUG packaging: disabling repo fedora
   09:34:37,313 DEBUG packaging: disabling repo updates-testing
   09:34:37,314 DEBUG packaging: disabling repo updates
   

3. The installation completes and the new system initiates boot properly