From Fedora Project Wiki

Associated release criterion
This test case is associated with the Basic_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.


This test will verify that anaconda can download the requested updates.img file using a HTTP/HTTPS url.


  1. There is an updates.img prepared for you in this test case. 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 in pyanaconda/ui/gui/spokes/, as this text is displayed on one of the first screens. Then host the updates.img on a httpd server accessible by your installation.

How to test

  1. Boot the installer while specifying the HTTP URL for the updates image. Use our provided one:
    or your own one.
  2. If it's possible, visually identify that the update was applied. With the update above, go to the Installation destination dialog and see that the disk capacity text has a pink background instead of the default gray background:
    Default look
    Updated look
  3. 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. (Please note if your updates.img doesn't change any source code files, but e.g. just an image, then the /tmp/updates directory is not created.)
  4. Proceed with installation

Expected Results

  1. 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).
  2. Anaconda proceeds without related errors