From Fedora Project Wiki

No longer current
The compose for which this page contains results is no longer the current one. This page contains the results for the current compose.

This page records Cloud validation testing test results for the Fedora 32 20200404.n.0 nightly compose.

Which tests to run[edit]

Test coverage page
This page provides information about test coverage for the tests on this page across all the composes for the current release: it can help you see which test cases most need to be run.

Tests with a Milestone of Basic, Beta or Final are the most important. Optional tests are less so, but still useful to run. The milestone indicates that for that milestone release or a later one to be approved for release, the test must have been run against the release candidate build (so at Beta, all Basic and Beta tests must have been run, for instance). However, it is important to run the tests for all milestones as early and often as possible. Please refer to the test coverage page linked above and try to find and run tests which have not been run at all, or not run recently, for the current release.

How to test[edit]

1. Download one or more media for testing, or for EC2 tests, locate and use an appropriate AMI:

Image aarch64 armhfp ppc64le s390x x86_64
Everything boot Download Download Download Download Download
Workstation live Download Download
Server dvd Download Download Download Download Download
Server boot Download Download Download Download Download
Cloud_Base qcow2 Download Download Download Download
Cloud_Base raw-xz Download Download Download Download
Cloud_Base vmdk Download Download Download Download
Cloud_Base vagrant-libvirt Download
Cloud_Base vagrant-virtualbox Download
KDE live Download
Xfce live Download
SoaS live Download
Mate live Download
Cinnamon live Download
LXDE live Download
Container_Base docker Download Download Download Download
Container_Minimal_Base docker Download Download Download Download
Python_Classroom vagrant-libvirt Download
Python_Classroom vagrant-virtualbox Download
Astronomy_KDE live Download
Comp_Neuro live Download
Design_suite live Download
Games live Download
Jam_KDE live Download
Python_Classroom live Download
Security live Download
Silverblue dvd-ostree Download Download Download
LXQt live Download
Workstation raw-xz Download Download
Server raw-xz Download Download
KDE raw-xz Download
Minimal raw-xz Download Download
Xfce raw-xz Download Download
SoaS raw-xz Download
Mate raw-xz Download
LXDE raw-xz Download
Python_Classroom raw-xz Download
LXQt raw-xz Download

x86_64 hvm standard AMIs[edit]

Region AMI ID Direct launch link
ap-northeast-1 ami-0d70181664be8e5f2 Launch in EC2
ap-northeast-2 ami-062ed4568b4399c71 Launch in EC2
ap-south-1 ami-0412e81270721f437 Launch in EC2
ap-southeast-1 ami-0b965838d52ce4f79 Launch in EC2
ap-southeast-2 ami-015aa8b8c675f3d95 Launch in EC2
ca-central-1 ami-0633e16dc6557c1d3 Launch in EC2
eu-central-1 ami-098371c1c08b704bf Launch in EC2
eu-west-1 ami-01518d6529e17f7a5 Launch in EC2
eu-west-2 ami-032c231d280de9349 Launch in EC2
sa-east-1 ami-0e759685eccc0cf1b Launch in EC2
us-east-1 ami-047e4ffab5f7dbcf5 Launch in EC2
us-east-2 ami-06a62c3293441d9a2 Launch in EC2
us-west-1 ami-016a50f643021f0be Launch in EC2
us-west-2 ami-00e74d15c92e020de Launch in EC2

x86_64 hvm gp2 AMIs[edit]

Region AMI ID Direct launch link
ap-northeast-1 ami-0f11f39688b2368f1 Launch in EC2
ap-northeast-2 ami-01d3acea263850fd0 Launch in EC2
ap-south-1 ami-0e3180cf26ba13667 Launch in EC2
ap-southeast-1 ami-01d90deeaeb2e1e7b Launch in EC2
ap-southeast-2 ami-06b4cfd0a509cdf7e Launch in EC2
ca-central-1 ami-0f0a2fb65af6a4bb2 Launch in EC2
eu-central-1 ami-0f0328ef3fb76b5bc Launch in EC2
eu-west-1 ami-0a9fa29e106e23fb3 Launch in EC2
eu-west-2 ami-0ff0c53ff67af843b Launch in EC2
sa-east-1 ami-09adc4c868e37cfec Launch in EC2
us-east-1 ami-036c1fdf46f4182e6 Launch in EC2
us-east-2 ami-0689a9761b758d9c5 Launch in EC2
us-west-1 ami-01d6d8347d6d97d8f Launch in EC2
us-west-2 ami-0a91f98a73c112755 Launch in EC2

arm64 hvm standard AMIs[edit]

Region AMI ID Direct launch link
ap-northeast-1 ami-082e595b46c5b2055 Launch in EC2
ap-northeast-2 ami-029fcebd4d47e8176 Launch in EC2
ap-south-1 ami-04157c35e08065b90 Launch in EC2
ap-southeast-1 ami-0d16ce60cc0478c8c Launch in EC2
ap-southeast-2 ami-0c55d3a0afb277441 Launch in EC2
ca-central-1 ami-0e21b8fbcdae4d200 Launch in EC2
eu-central-1 ami-0d95cf0d7cb60f565 Launch in EC2
eu-west-1 ami-06fe0c2637d7e2080 Launch in EC2
eu-west-2 ami-0d96cfb2f34953e2a Launch in EC2
sa-east-1 ami-0ceada058a27c4ed5 Launch in EC2
us-east-1 ami-03faea7532fd68544 Launch in EC2
us-east-2 ami-062e6e0dd5cbcd6ee Launch in EC2
us-west-1 ami-035dc05a0a708307c Launch in EC2
us-west-2 ami-0070444a790046508 Launch in EC2

arm64 hvm gp2 AMIs[edit]

Region AMI ID Direct launch link
ap-northeast-1 ami-0b67953d5a9625890 Launch in EC2
ap-northeast-2 ami-0a5b5ab824f0195fc Launch in EC2
ap-south-1 ami-07c75a536db084cd8 Launch in EC2
ap-southeast-1 ami-0e8c38c38d1df1f0d Launch in EC2
ap-southeast-2 ami-0316024b2f7ac7026 Launch in EC2
ca-central-1 ami-070d3c1bfb08a2060 Launch in EC2
eu-central-1 ami-0d20a95084c8c3dad Launch in EC2
eu-west-1 ami-0789a1a7773b4949c Launch in EC2
eu-west-2 ami-0add3749c00223e5d Launch in EC2
sa-east-1 ami-0854c2a85db9af6e9 Launch in EC2
us-east-1 ami-0b216256484447d1d Launch in EC2
us-east-2 ami-0733a00b2f5e66194 Launch in EC2
us-west-1 ami-0d54577ac00dd3d03 Launch in EC2
us-west-2 ami-0ad33ca7857205696 Launch in EC2

2. Perform one or more of the test cases and add your results to the table below

  • You can submit results by editing the page directly, or by using relval, with the relval report-results command. It provides a simple text interface for reporting test results.

3. If a test fails, file a bug report. You may propose the bug as a release blocker or freeze exception bug for the appropriate release - see blocker bug process and freeze exception bug process.

Some tests must be run against particular Products or images - for example, the #Default boot and install tests. If no particular product or image is specified either in this page or the test case page, you can use any appropriate image. For example, you can run most of the #General Tests with the Workstation live image, or either of the Server install images.

If you notice a problem during a test which does not constitute a complete failure of the test, you should still file a bug report, but it may not be appropriate to propose it as a release blocker bug. Use your judgment in deciding this, with reference to the Fedora_Release_Criteria, which these tests are intended to verify. If you are unsure, err on the side of proposing the bug as a blocker.

Don't install updates
Don't install updates before performing any of the tests, as when you are testing pre-releases, available updates are not part of the proposed released package set.
Virtual machine testing
In most cases, testing in a virtual machine is OK. You can test UEFI (including SecureBoot) in VMs as well.

Results summary page[edit]

The Test Results:Fedora 32 Branched 20200404.n.0 Summary page contains the results from this page and all the other validation pages for the same compose listed together to provide an overview.

Add, Modify or Remove a Test Case[edit]

  1. Please request review for your changes by publishing your test case for review to the test mailing list and/or the appropriate working group mailing list (e.g. server, cloud, or desktop).
  2. Once reviewed, make your changes to any current documents that use the template (e.g. Test_Results:Current_Cloud_Test).
  3. Lastly, update Template:Cloud_test_matrix with the same changes.


See the table below for a sample format for test results. All test results are posted using the result template.

Test Result Explanation Code Entered
Untested - This test has not been run, and is available for anyone to contribute feedback. {{result|none}}
Pass pass robatino
Passed - The test has been run and the tester determine the test met the expected results {{result|pass|robatino}}
Inprogress inprogress adamwill
Inprogress - An inprogress result is often used for tests that take a long time to execute. Inprogress results should be temporary and change to pass, fail or warn. {{result|inprogress|adamwill}}
Fail fail jlaska [1] [2]
Failed - Indicates a failed test. A link to a bug must be provided. See Template:Result for details on providing bug information.
  1. RHBZ #XYZ
  2. RHBZ #ZXY
Warning warn rhe
Warning - This test completed and met the expected results of the test, but other issues were encountered during testing that warrant attention.
  1. Brief description about the warning status
{{result|warn|rhe}} <ref>Brief description about the warning status</ref>
Pass pass hongqing
Warning warn kparal
Multiple results - More people can easily provide results to a single test case. {{result|pass|hongqing}} {{result|warn|kparal}}
Pass pass previous <build> run
Result from previous test run - This test result is directly moved from the test run of previous <build>. {{result|pass|previous <build> run}}
Unsupported - An unsupported test or configuration. No testing is required.

Test Matrix[edit]

Cloud Provider Setup[edit]

Expand one of the sections below for instructions on getting set up to run these testcases on a specific provider. More information can be found in the Fedora Cloud guide.

Amazon EC2

  1. Get an AWS account (the approval process can take hours)
  2. Make sure that your security group allows for SSH (default tcp port 22)
  3. Log in to the AWS Management Console
  4. Obtain the AMI id of the image you want to test. For officially released images, check If you're doing validation testing, there should be some tables of AMI IDs above; if not, try looking through the messages published by the AMI publisher
  5. Search for and select the desired AMI on the IMAGES/AMIs section of the EC2 console
  6. Launch an instance with the AMI under test

Amazon provided this information on various instance types that may be useful to test, in August 2019. Note that you can use 750 hours per month on a t2.micro instance (which is Xen-based) for free for the first year; other instance types, and t2.micro after the first year, cost money. To avoid costs, you can contact the the Infrastructure team and request access to Fedora's AWS account for testing purposes, per this SOP.

x86 platforms

  • Xen domU with only PV interfaces (e.g., M3 instances)
  • Xen domU with Intel 82599 virtual functions for Enhanced Networking (e.g., C3 instances running in a VPC)
  • Xen domU with Enhanced Networking Adapter (e.g., R4 instances)
  • Xen domU with NVMe local instance storage (e.g., virtualized I3 instances)
  • Xen domU with more than 32 vCPUs (e.g., c4.8xlarge)
  • Xen domU with four NUMA nodes (e.g., x1.32xlarge)
  • Xen domU with maximum RAM available in EC2 (x1e.32xlarge)
  • KVM guest with consistent performance (e.g., c5.large)
  • KVM guest with burstable performance (e.g., t3.large)
  • KVM guest with local NVMe storage (e.g., c5d.large)
  • KVM guest with 100 Gbps networking and Elastic Fabric Adapter (c5n.18xlarge)
  • KVM guest on AMD processors (e.g., m5a.large)
  • KVM guest on AMD processors with maximum NUMA nodes (e.g., m5a.24xlarge)
  • Bare metal Broadwell (i3.metal)
  • Bare metal Skylake (m5.metal)
  • Bare metal Cascade Lake (c5.metal)

Arm platforms

  • KVM guest on Arm with 1 CPU cluster (a1.xlarge)
  • KVM guest on Arm with 2 CPU clusters (a1.2xlarge)
  • KVM guest on Arm with 4 CPU clusters (a1.4xlarge)


  1. Use your own OpenStack deployment
  2. Provide or create an SSH keypair
  3. Make sure that your security group allows for SSH (default tcp port 22)
  4. Log in to the Horizon dashboard
  5. Find the image URL at or as provided in release candidate documents.
  6. Add the image to OpenStack, either using the OpenStack web dashboard (see step 4 here) or with glance image-create --name "Fedora version" --disk-format qcow2 --container-format bare --is-public true --copy-from url
  7. Launch the instance (in the dashboard, under the "Images" heading, click the "Launch" button for the appropriate image

Local testing

  1. You can deploy the cloud image locally either using the well-known virt-install tool or a Fedora-specific testcloud tool. See Local cloud testing with virt-install or Testcloud quickstart guide, respectively.
  2. Once logged in the virtual cloud instance, you can perform the tests below.


Milestone Test Case Local EC2 (KVM) EC2 (Xen) Openstack
Basic QA:Testcase_base_startup
Bot Pass pass coconut
Basic QA:Testcase_base_system_logging
Bot Pass pass coconut
Final QA:Testcase_base_services_start
Bot Pass pass coconut
Final QA:Testcase_base_selinux
Bot Pass pass coconut
Final QA:Testcase_base_service_manipulation
Bot Pass pass coconut


Milestone Test Case Local EC2 (KVM) Openstack
Basic QA:Testcase_base_startup
Pass pass pwhalen
Basic QA:Testcase_base_system_logging
Pass pass pwhalen
Final QA:Testcase_base_services_start
Warning warn pwhalen
Final QA:Testcase_base_selinux
Pass pass pwhalen
Final QA:Testcase_base_service_manipulation
  1. dnf-makecache.service failed