From Fedora Project Wiki

(clarify repo architecture)
No edit summary
 
(6 intermediate revisions by 2 users not shown)
Line 1: Line 1:
{{Template:Associated_release_criterion|Beta|remote-package-sources}}
{{QA/Test_Case
{{QA/Test_Case
|description=This is to verify that an installation can be performed from a NFS repository configured in the [[Anaconda]] GUI.
|description=This is to verify that an installation can be performed from a NFS repository configured in the [[Anaconda]] GUI.
|setup=
|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:
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}}
* Mount the image over loopback: {{command|# mount -o loop Fedora-{{FedoraVersionNumber|next}}-x86_64-DVD.iso /mnt/repo}}
#* Install {{package|nfs-utils}}.
* Install {{package|nfs-utils}}.
#* Let's say your (virtual) test machine is in the <code>192.168.1.0/24</code> subnet. Put the following line into {{filename|/etc/exports}}: <pre>/mnt/repo    192.168.1.0/24(ro)</pre>
* 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}}:
#* Restart NFS service: {{command|# systemctl restart nfs-server.service}}
<pre>
#* The repository is now accessible over NFS via <code>&lt;your_IP&gt;:/mnt/repo</code>
/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 the installer using any available non-live means (anything except {{filename|Live.iso}})
# Boot the installer using any available non-live means (anything except {{filename|Live.iso}})
# Change the installation source to point to a custom NFS repository
# Change the installation source to point to a custom NFS repository
#* The correct syntax is <code>server:/path</code>, e.g. <code>&lt;your_IP&gt;:/mnt/repo</code>
#* The correct syntax is <code>server:/path</code>, e.g. <code>&lt;your_IP&gt;:/repo</code>
#* Make sure the repository architecture matches the architecture of your installer media.
#* Make sure the repository architecture matches the architecture of your installer media.
# Proceed with installation
# Proceed with installation
Line 18: Line 24:
<li>The installer accepts the NFS repository definition</li>
<li>The installer accepts the NFS repository definition</li>
<li>The said repository is used for installation. This can be checked by examining the {{filename|/tmp/packaging.log}} file. Example output:
<li>The said repository is used for installation. This can be checked by examining the {{filename|/tmp/packaging.log}} file. Example output:
<pre>14:44:07,093 INFO packaging: mounting 192.168.1.1:/mnt/repo: on /mnt/install/source
<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,545 DEBUG packaging: adding yum repo anaconda with baseurl file:///mnt/install/source and mirrorlist None

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