QA:Testcase install repository HTTP/FTP variation

From FedoraProject

(Difference between revisions)
Jump to: navigation, search
(add the 'associated criterion' block)
(adjust associated_release_criterion template invocation)
Line 1: Line 1:

Revision as of 21:04, 30 July 2013

Associated release criterion
This test case is associated with the Fedora_23_Alpha_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.



This is to verify that Anaconda's inst.repo boot option works together with an HTTP(S) or FTP repository.


  1. Prepare any non-live media for booting the installer (anything except Live.iso).

How to test

  1. Before booting the installer, specify a target HTTP/FTP repository by adding a following boot option:
    • For HTTP or HTTPS:
    • For FTP:
    • If proxy is needed, add it as another option:
    • Example: Use
    • Make sure the repository architecture matches the architecture of your installer media.
  2. Proceed with installation.

Expected Results

  1. The installer auto-selects requested HTTP/FTP 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 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