From Fedora Project Wiki
(link out to the anaconda/updates page for up-to-date creation instructions) |
(mention the option to use compose files, without the need of mirroring the whole branched repository) |
||
Line 1: | Line 1: | ||
{{QA/Test_Case | {{QA/Test_Case | ||
|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. For help preparing {{filename|updates.img}}, see [[Anaconda/Updates]] | |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. For help preparing {{filename|updates.img}}, see [[Anaconda/Updates]] | ||
| | |setup= | ||
# Prepare a local installation source by mirroring an [http://mirrors.fedoraproject.org/ | # Prepare a local installation source by mirroring an existing online source. You can either mirror a whole repository for Fedora Branched, or you can mirror just a single test compose. | ||
#* When mirroring the whole Fedora Branched repository, mirror {{filename|/pub/fedora/linux/development/{{FedoraVersionNumber|next}}/<arch>/os/}} directory from one of the [http://mirrors.fedoraproject.org/ official mirrors]. This amounts to dozens of GBs of space, but you will be able to use a standard {{filename|netinst.iso}}/{{filename|DVD.iso}}/{{filename|Live.iso}} with it. | |||
#* When mirroring a single test compose, mirror {{filename|/Fedora/<arch>/os/}} directory from the compose. This is just hundreds of MBs, but you will need to use direct kernel boot (PXE or a kernel boot in a virtual machine) to test it. | |||
# 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. See [[Anaconda/Updates#create-images|this page]] for image creation instructions. A good thing to change in the {{filename|updates.img}} is the "What language would you like to use during the installation process?" text in {{filename|pyanaconda/iw/language_gui.py}}, as this text is displayed on one of the first screens. | # Prepare a valid {{filename|updates.img}} file. See [[Anaconda/Updates#create-images|this page]] for image creation instructions. A good thing to change in the {{filename|updates.img}} is the "What language would you like to use during the installation process?" text in {{filename|pyanaconda/iw/language_gui.py}}, 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 | ||
|actions= | |||
# Boot the installer using the <code>inst.repo=</code> option at boot directing to the modified installation source where the {{filename|updates.img}} was published. See [[Anaconda/Options]] for information on supported boot options. | # Boot the installer using the <code>inst.repo=</code> option at boot directing to the modified installation source where the {{filename|updates.img}} was published. See [[Anaconda/Options]] for information on supported boot options. | ||
#* If you have a full repository mirrored, you can use any boot medium. | |||
#* If you have just a test compose files mirrored, you need to use direct kernel boot (PXE or a kernel boot in a virtual machine). It will use the provided <code>inst.repo</code> as a source of Anaconda's stage2 image and it should also apply {{filename|updates.img}}, if available. The online repositories will then be used as the package source. | |||
# Proceed with installation | # Proceed with installation | ||
|results= | |results= |
Revision as of 13:53, 22 January 2013
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. For help preparing updates.img
, see Anaconda/Updates
Setup
- Prepare a local installation source by mirroring an existing online source. You can either mirror a whole repository for Fedora Branched, or you can mirror just a single test compose.
- When mirroring the whole Fedora Branched repository, mirror
/pub/fedora/linux/development/41/<arch>/os/
directory from one of the official mirrors. This amounts to dozens of GBs of space, but you will be able to use a standardnetinst.iso
/DVD.iso
/Live.iso
with it. - When mirroring a single test compose, mirror
/Fedora/<arch>/os/
directory from the compose. This is just hundreds of MBs, but you will need to use direct kernel boot (PXE or a kernel boot in a virtual machine) to test it.
- When mirroring the whole Fedora Branched repository, mirror
- Make the installation source accessible over one of the supported network protocols (HTTP, FTP, NFS).
- Prepare a valid
updates.img
file. See this page for image creation instructions. A good thing to change in theupdates.img
is the "What language would you like to use during the installation process?" text inpyanaconda/iw/language_gui.py
, as this text is displayed on one of the first screens. - Copy the
updates.img
into theimages/
directory of your local installation source
How to test
- Boot the installer using the
inst.repo=
option at boot directing to the modified installation source where theupdates.img
was published. See Anaconda/Options for information on supported boot options.- If you have a full repository mirrored, you can use any boot medium.
- If you have just a test compose files mirrored, you need to use direct kernel boot (PXE or a kernel boot in a virtual machine). It will use the provided
inst.repo
as a source of Anaconda's stage2 image and it should also applyupdates.img
, if available. The online repositories will then be used as the package source.
- Proceed with installation
Expected Results
- Anaconda prepares the
updates.img
and copies its content to/tmp/updates/
. Any changes you included in the updates.img file are applied - Anaconda proceeds without related errors