QA:Testcase Anaconda updates.img via installation source

From FedoraProject

(Difference between revisions)
Jump to: navigation, search
(adjust associated_release_criterion template invocation)
m (TCs now contain full repo, advise what to exclude)
Line 6: Line 6:
 
# 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.
 
# 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 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.
+
#* When mirroring a single test compose, mirror {{filename|/Fedora/<arch>/os/}} directory from the compose, but exclude {{filename|repodata/}} and {{filename|Packages/}} subdirectories. 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/ui/gui/spokes/welcome.glade}}, 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/ui/gui/spokes/welcome.glade}}, as this text is displayed on one of the first screens.

Revision as of 14:04, 25 November 2013

Note.png
Associated release criterion
This test case is associated with the Fedora_21_Final_Release_Criteria#update-image 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.


Contents

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

  1. 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/21/<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 standard netinst.iso/DVD.iso/Live.iso with it.
    • When mirroring a single test compose, mirror /Fedora/<arch>/os/ directory from the compose, but exclude repodata/ and Packages/ subdirectories. 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.
  2. Make the installation source accessible over one of the supported network protocols (HTTP, FTP, NFS).
  3. Prepare a valid updates.img file. See this page for image creation instructions. A good thing to change in the updates.img is the "What language would you like to use during the installation process?" text in pyanaconda/ui/gui/spokes/welcome.glade, as this text is displayed on one of the first screens.
  4. Copy the updates.img into the images/ directory of your local installation source

How to test

  1. Boot the installer using the inst.stage2= option at boot directing to the modified installation source where the 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 inst.repo as a source of Anaconda's stage2 image and it should also apply updates.img, if available. The online repositories will then be used as the package source.
  2. Proceed with installation

Expected Results

  1. Anaconda prepares the updates.img and copies its content to /tmp/updates/. Any changes you included in the updates.img file are applied
  2. Anaconda proceeds without related errors