From Fedora Project Wiki

(added ftp server as another choice of repo)
(clarify HTTPS and drop FTP, per https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org/thread/KJAUUCMCG2IAEAXH6OQMX45KWOFTWANB/)
 
(9 intermediate revisions by 2 users not shown)
Line 1: Line 1:
{{Template:Associated_release_criterion|Alpha|remote-package-sources}}
{{QA/Test_Case
{{QA/Test_Case
|description=This test case verifies the HTTP(or FTP)-based package repository through graphical repository dialog during installation. Testing also includes verifying proper installation of packages included in the repository.  While any HTTP package repository would satisfy this test, a custom repository is provided for convenience.
|description=This is to verify that an installation can be performed from a HTTP/HTTPS repository configured in the [[Anaconda]] GUI.
|actions=
|actions=
# Boot the installer using any available means ({{filename|netinst.iso}}, pxeboot images or {{filename|DVD.iso}})
# Boot the installer using any available non-live means (anything except {{filename|Live.iso}})
# Proceed through the installer until the ''Software Selection'' step
# Change the installation source to point to a custom HTTP/HTTPS repository
# At the software selection step, click ''Add additional software repositories'' and provide the information listed. You may also click ''Modify repository'' to replace an existing entry. Enter the following information, then select ''OK''
#* You can pick one from the [https://mirrors.fedoraproject.org/mirrorlist?repo=fedora-{{FedoraVersionNumber|next}}&arch=x86_64 list of mirrors] or you can use the default redirect https://download.fedoraproject.org/pub/fedora/linux/development/{{FedoraVersionNumber|next}}/x86_64/os (change the architecture to match the architecture of your installation media, if needed).
#* ''Repository type'' - HTTP/FTP
# Proceed with installation
#* ''Repository URL'' - http://rhe.fedorapeople.org/repotest
#* Uncheck ''URL is a mirror list''
#* If you have a proxy, configure a proxy as needed
# Select ''Customize now'', then click ''next''
# Select the group ''Repo Test'' and check several packages for installation.
|results=
|results=
# The package metadata from the HTTP(or FTP) repository is read correctly
<ol>
# The expected packages or package groups provided by additional repository appear on the package detail screen
<li>The installer accepts the HTTP/HTTPS repository definition</li>
#* If using the package repository listed above, the group ''Repo Test'' and its packages are listed.
<li>The said repository is used for installation. This can be checked by examining the {{filename|/tmp/packaging.log}} file. Example output:
# Anaconda completes and system reboots successfully
{{#tag:pre|
# The checked packages provided by additional repository are installed in the system
09:34:37,295 DEBUG packaging: adding yum repo anaconda with baseurl http://download.fedoraproject.org/pub/fedora/linux/development/{{FedoraVersionNumber|next}}/x86_64/os and mirrorlist None
#* If using the package repository listed above, {{filename|kong-0.1-1.noarch}} and {{filename|bixu-0.1-1.noarch}} are installed by default.
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
}}</li>
<li>The installation completes and the new system initiates boot properly</li>
</ol>
}}
}}
[[Category:Repository]]
[[Category:Repository]]
[[Category:Installation Repository HTTP/FTP]]
[[Category:Installation Repository HTTP]]

Latest revision as of 09:32, 7 January 2021

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/HTTPS 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/HTTPS repository
  3. Proceed with installation

Expected Results

  1. The installer accepts the HTTP/HTTPS 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/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
Retrieved from "https://fedoraproject.org/w/index.php?title=QA:Testcase_install_repository_HTTP_graphical&oldid=599789"