From Fedora Project Wiki

(add the 'associated criterion' block)
(adjust associated_release_criterion template invocation)
Line 1: Line 1:
{{Template:Associated_release_criterion|releasecriterion=Fedora_{{FedoraVersionNumber|next}}_Alpha_Release_Criteria#Remote_package_sources}}
{{Template:Associated_release_criterion|Alpha|remote-package-sources}}


{{QA/Test_Case
{{QA/Test_Case

Revision as of 20:57, 30 July 2013

Note.png
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 an installation can be performed from a HTTP/FTP repository configured in the Anaconda GUI.


How to test

  1. Boot the installer using any available non-live means (anything except Live.iso)
  2. Change the installation source to point to a custom HTTP/FTP repository
  3. Proceed with installation

Expected Results

  1. The installer accepts the HTTP/FTP repository definition
  2. The said repository is used for installation. This can be checked by examining the /tmp/packaging.log file. Example output:
    09:34:37,295 DEBUG packaging: adding yum repo anaconda with baseurl http://download.fedoraproject.org/pub/fedora/linux/development/40/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