From Fedora Project Wiki

m (moved QA:Testcase Additional NFS Repository to QA:Testcase install repository NFS graphical: Integrated the graphical repository tests to 'install repository' category)
No edit summary
 
(13 intermediate revisions by 3 users not shown)
Line 1: Line 1:
{{Template:Associated_release_criterion|Beta|remote-package-sources}}
{{QA/Test_Case
{{QA/Test_Case
|description=This test case exercises the addition of a NFS-based package repository during installation. Testing also includes verifying proper installation of packages included in the repository.
|description=This is to verify that an installation can be performed from a NFS repository configured in the [[Anaconda]] GUI.
|setup=
You need to have a Fedora repository accessible over an NFS protocol. If you do have it, no further setup is needed. If you don't, you can mount a {{filename|DVD.iso}} image and export it over NFS this way:
* Mount the image over loopback: {{command|# mount -o loop Fedora-{{FedoraVersionNumber|next}}-x86_64-DVD.iso /mnt/repo}}
* Install {{package|nfs-utils}}.
* Let's say your (virtual) test machine is in the <code>192.168.122.0/24</code> subnet. Put the following lines into {{filename|/etc/exports}}:
<pre>
/mnt        192.168.122.0/24(ro,fsid=0)
/mnt/repo    192.168.122.0/24(ro)
</pre>
* Restart NFS service: {{command|# systemctl restart nfs-server.service}}
* The repository is now accessible over NFS via <code>&lt;your_IP&gt;:/repo</code>
|actions=
|actions=
# Boot and initiate an install using any installation source (e.g. {{filename|boot.iso}}, CD, DVD or pxeboot)
# 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 NFS repository
# At the software selection step, click ''Add additional software repositories'' and provide the information listed.  If more than one package repository is listed, you may also click ''Modify repository'' for an existing unselected entry.  Enter the following information, then select ''OK''
#* The correct syntax is <code>server:/path</code>, e.g. <code>&lt;your_IP&gt;:/repo</code>
#* ''Repository type'' - NFS
#* Make sure the repository architecture matches the architecture of your installer media.
#* ''Server'' - <pre>host.domain.tld</pre>
# Proceed with installation
#* ''Path'' - <pre>/path/to/repo</pre>
# Select ''Customize now'', then click ''next''
# Check several packages or package groups provided by the additional repository on the screen
|results=
|results=
# The package metadata from additional 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 NFS repository definition</li>
# Anaconda completes and system reboots successfully
<li>The said repository is used for installation. This can be checked by examining the {{filename|/tmp/packaging.log}} file. Example output:
# The checked packages provided by additional repository are installed in the system  
<pre>14:44:07,093 INFO packaging: mounting 192.168.122.1:/repo: on /mnt/install/source
...
14:44:07,545 DEBUG packaging: adding yum repo anaconda with baseurl file:///mnt/install/source and mirrorlist None
14:44:07,568 DEBUG packaging: disabling repo fedora
14:44:07,569 DEBUG packaging: disabling repo updates-testing
14:44:07,569 DEBUG packaging: disabling repo updates</pre></li>
<li>The installation completes and the new system initiates boot properly</li>
</ol>
}}
}}
[[Category:Repository]]
[[Category:Repository]]
[[Category:Installation Repository NFS]]

Latest revision as of 09:09, 8 April 2015

Note.png
Associated release criterion
This test case is associated with the Fedora_40_Beta_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 NFS repository configured in the Anaconda GUI.

Setup

You need to have a Fedora repository accessible over an NFS protocol. If you do have it, no further setup is needed. If you don't, you can mount a DVD.iso image and export it over NFS this way:

  • Mount the image over loopback: # mount -o loop Fedora-40-x86_64-DVD.iso /mnt/repo
  • Install Package-x-generic-16.pngnfs-utils.
  • Let's say your (virtual) test machine is in the 192.168.122.0/24 subnet. Put the following lines into /etc/exports:
/mnt         192.168.122.0/24(ro,fsid=0)
/mnt/repo    192.168.122.0/24(ro)
  • Restart NFS service: # systemctl restart nfs-server.service
  • The repository is now accessible over NFS via <your_IP>:/repo

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 NFS repository
    • The correct syntax is server:/path, e.g. <your_IP>:/repo
    • Make sure the repository architecture matches the architecture of your installer media.
  3. Proceed with installation

Expected Results

  1. The installer accepts the NFS repository definition
  2. The said repository is used for installation. This can be checked by examining the /tmp/packaging.log file. Example output: 
    14:44:07,093 INFO packaging: mounting 192.168.122.1:/repo: on /mnt/install/source
...
14:44:07,545 DEBUG packaging: adding yum repo anaconda with baseurl file:///mnt/install/source and mirrorlist None
14:44:07,568 DEBUG packaging: disabling repo fedora
14:44:07,569 DEBUG packaging: disabling repo updates-testing
14:44:07,569 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_NFS_graphical&oldid=409210"