From Fedora Project Wiki
(link to Testcase_Anaconda_updates.img_via_URL for a prepared updates.img) |
(simplify and update for F21) |
||
Line 4: | Line 4: | ||
|description=This test will verify that anaconda can download and apply a {{filename|updates.img}} that is inside the remote installation source without extra input from the user. | |description=This test will verify that anaconda can download and apply a {{filename|updates.img}} that is inside the remote installation source without extra input from the user. | ||
|setup= | |setup= | ||
# Prepare a local installation source by mirroring | # Prepare a local installation source by mirroring {{filename|Server/<arch>/os/}} directory from the test compose in question. | ||
#* You can choose to exclude {{filename|Packages/}} and {{filename|repo*/}} subdirectories. In that case it won't work as a proper repository and you'll need to instruct anaconda to use this location just for fetching its stage2 image. | |||
#* | |||
# Make the installation source accessible over one of the supported network protocols (HTTP, FTP, NFS). | # Make the installation source accessible over one of the supported network protocols (HTTP, FTP, NFS). | ||
# Prepare a valid {{filename|updates.img}} file. There is an {{filename|updates.img}} prepared for you in [[QA:Testcase Anaconda updates.img via URL|this test case]]. You can use it and follow the same steps to verify that it is applied. If it doesn't work or you want to use a different one, see [[Anaconda/Updates#create-images|this page]] for image creation instructions, and prepare your own file. A good thing to change in the image is the ''What language would you like to use during the installation process?'' text in {{filename|pyanaconda/ui/gui/spokes/welcome.glade}}, as this text is displayed on one of the first screens. | # Prepare a valid {{filename|updates.img}} file. There is an {{filename|updates.img}} prepared for you in [[QA:Testcase Anaconda updates.img via URL|this test case]]. You can use it and follow the same steps to verify that it is applied. If it doesn't work or you want to use a different one, see [[Anaconda/Updates#create-images|this page]] for image creation instructions, and prepare your own file. A good thing to change in the image is the ''What language would you like to use during the installation process?'' text in {{filename|pyanaconda/ui/gui/spokes/welcome.glade}}, as this text is displayed on one of the first screens. | ||
# Copy the {{filename|updates.img}} into the {{filename|images/}} directory of your local installation source | # Copy the {{filename|updates.img}} into the {{filename|images/}} directory of your local installation source. The file needs to be named {{filename|updates.img}}, nothing else is recognized. | ||
|actions= | |actions= | ||
# Boot the installer using the <code>inst. | # Boot the installer using any non-Live means (i.e. DVD, netinst, PXE boot) using the <code>inst.repo=</code> option at boot directing to the modified installation source where the {{filename|updates.img}} was published. Example: <pre>inst.repo=http://myserver/Server/x86_64/os/</pre> If you have excluded packages while mirroring the test compose, you need to use <code>inst.stage2=</code> instead. Example: <pre>inst.stage2=http://myserver/Server/x86_64/os/</pre> In this case you can add an additional <code>inst.repo=</code> argument to specify a concrete repo location. See [[Anaconda/Options]] for information on supported boot options. | ||
# If it's possible, visually identify that the update was applied. If you have used the prepared {{filename|updates.img}} from [[QA:Testcase Anaconda updates.img via URL|this test case]], follow its relevant steps to verify it applied correctly. | # If it's possible, visually identify that the update was applied. If you have used the prepared {{filename|updates.img}} from [[QA:Testcase Anaconda updates.img via URL|this test case]], follow its relevant steps to verify it applied correctly. | ||
# If it's not visually possible to confirm the update was applied (there were just code changes), verify the existence of {{filename|/tmp/updates}} directory, which should contain all updated source code files. | # If it's not visually possible to confirm the update was applied (there were just code changes), verify the existence of {{filename|/tmp/updates}} directory, which should contain all updated source code files. |
Revision as of 11:14, 12 November 2014
Description
This test will verify that anaconda can download and apply a updates.img
that is inside the remote installation source without extra input from the user.
Setup
- Prepare a local installation source by mirroring
Server/<arch>/os/
directory from the test compose in question.- You can choose to exclude
Packages/
andrepo*/
subdirectories. In that case it won't work as a proper repository and you'll need to instruct anaconda to use this location just for fetching its stage2 image.
- You can choose to exclude
- Make the installation source accessible over one of the supported network protocols (HTTP, FTP, NFS).
- Prepare a valid
updates.img
file. There is anupdates.img
prepared for you in this test case. You can use it and follow the same steps to verify that it is applied. If it doesn't work or you want to use a different one, see this page for image creation instructions, and prepare your own file. A good thing to change in the image is the What language would you like to use during the installation process? text inpyanaconda/ui/gui/spokes/welcome.glade
, as this text is displayed on one of the first screens. - Copy the
updates.img
into theimages/
directory of your local installation source. The file needs to be namedupdates.img
, nothing else is recognized.
How to test
- Boot the installer using any non-Live means (i.e. DVD, netinst, PXE boot) using the
inst.repo=
option at boot directing to the modified installation source where theupdates.img
was published. Example:inst.repo=http://myserver/Server/x86_64/os/
If you have excluded packages while mirroring the test compose, you need to useinst.stage2=
instead. Example:inst.stage2=http://myserver/Server/x86_64/os/
In this case you can add an additionalinst.repo=
argument to specify a concrete repo location. See Anaconda/Options for information on supported boot options. - If it's possible, visually identify that the update was applied. If you have used the prepared
updates.img
from this test case, follow its relevant steps to verify it applied correctly. - If it's not visually possible to confirm the update was applied (there were just code changes), verify the existence of
/tmp/updates
directory, which should contain all updated source code files. - Proceed with installation
Expected Results
- Anaconda downloads the
updates.img
and copies its content to/tmp/updates/
. Any changes you included in the updates.img file are applied (image changes, text adjustments, source code changes, etc). - Anaconda proceeds without related errors