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 20191206.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 Alpha, 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 Alpha 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 s390x x86_64
Everything boot Download Download Download Download
Workstation live Download
Server dvd Download Download Download Download
Server boot Download Download Download Download
Cloud_Base qcow2 Download Download Download
Cloud_Base raw-xz Download Download Download
Cloud_Base vmdk Download Download Download
Cloud_Base vagrant-libvirt Download
Cloud_Base vagrant-virtualbox Download
KDE live Download
Xfce live Download
Mate live Download
LXDE live Download
Container_Base docker Download Download Download
Container_Minimal_Base docker Download Download Download
Python_Classroom vagrant-libvirt Download
Python_Classroom vagrant-virtualbox Download
Design_suite live Download
Python_Classroom 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
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-0c9aba5ec7f6536e6 Launch in EC2
ap-northeast-2 ami-05fb084eb1d000ab3 Launch in EC2
ap-south-1 ami-04e211782c406eb4f Launch in EC2
ap-southeast-1 ami-00559e819f2c2e661 Launch in EC2
ap-southeast-2 ami-0993a41e3bfb0916b Launch in EC2
ca-central-1 ami-08ed74367a16bc122 Launch in EC2
eu-central-1 ami-08d289d3a3e0ac74d Launch in EC2
eu-west-1 ami-0ec3ee35d971fbc2c Launch in EC2
eu-west-2 ami-0519dc6d94f9e43bd Launch in EC2
sa-east-1 ami-08bd0cf7ad9b58095 Launch in EC2
us-east-1 ami-02ed874c871c07330 Launch in EC2
us-east-2 ami-063b6c24a120e827e Launch in EC2
us-west-1 ami-0c532e8f54a263115 Launch in EC2
us-west-2 ami-0fd29af13e73c1b5e Launch in EC2

x86_64 hvm gp2 AMIs[edit]

Region AMI ID Direct launch link
ap-northeast-1 ami-06237c1ed90ebeb20 Launch in EC2
ap-northeast-2 ami-06785de4741a4f889 Launch in EC2
ap-south-1 ami-06cb00c74d8b2d150 Launch in EC2
ap-southeast-1 ami-0b0627ea57e03c71b Launch in EC2
ap-southeast-2 ami-0723002a85724124d Launch in EC2
ca-central-1 ami-0ce82e3cff4b267c8 Launch in EC2
eu-central-1 ami-031189b87f181e178 Launch in EC2
eu-west-1 ami-0e0b4d102b609d21c Launch in EC2
eu-west-2 ami-0d1062e5e14588def Launch in EC2
sa-east-1 ami-037079f606b335879 Launch in EC2
us-east-1 ami-04a25438d709f72f7 Launch in EC2
us-east-2 ami-0d2707805cce696c2 Launch in EC2
us-west-1 ami-0678214a08f22f3c1 Launch in EC2
us-west-2 ami-048ec11d3296c06ff Launch in EC2

arm64 hvm standard AMIs[edit]

Region AMI ID Direct launch link
ap-northeast-1 ami-03079f0b025147263 Launch in EC2
ap-northeast-2 ami-091e8f594014212d4 Launch in EC2
ap-south-1 ami-0d93ae36ceb971bb8 Launch in EC2
ap-southeast-1 ami-0a6fbce5d8794c874 Launch in EC2
ap-southeast-2 ami-0081fb3387905e293 Launch in EC2
ca-central-1 ami-0a665ebfab4b2ef69 Launch in EC2
eu-central-1 ami-0b31283aee8cd4f4d Launch in EC2
eu-west-1 ami-0afd65942c2e950a7 Launch in EC2
eu-west-2 ami-0347b6ad118ef5058 Launch in EC2
sa-east-1 ami-029a7c1ababbd2c13 Launch in EC2
us-east-1 ami-0a1bb04ddf3a1acbb Launch in EC2
us-east-2 ami-06da729f6fcc0b1de Launch in EC2
us-west-1 ami-0ac2011d83a2be962 Launch in EC2
us-west-2 ami-0a05da81c340af154 Launch in EC2

arm64 hvm gp2 AMIs[edit]

Region AMI ID Direct launch link
ap-northeast-1 ami-0e5755db26864170b Launch in EC2
ap-northeast-2 ami-0a90788546ff11df6 Launch in EC2
ap-south-1 ami-0433f7a38756a0005 Launch in EC2
ap-southeast-1 ami-03b0ee964deabdd30 Launch in EC2
ap-southeast-2 ami-082496c14047e9a1a Launch in EC2
ca-central-1 ami-0f8224f6cc21ee690 Launch in EC2
eu-central-1 ami-05dda9e2fc2f38713 Launch in EC2
eu-west-1 ami-01a079cab0325e8c4 Launch in EC2
eu-west-2 ami-01916cd763df09342 Launch in EC2
sa-east-1 ami-06c5a14e3de02c055 Launch in EC2
us-east-1 ami-04dcf80eb51452c18 Launch in EC2
us-east-2 ami-0f9b11c93d0349f31 Launch in EC2
us-west-1 ami-09bba8cd1cb559efd Launch in EC2
us-west-2 ami-06a03aec52196b883 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 Rawhide 20191206.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

Testcloud Local

  1. See Local Test Cloud Installation Guide for instructions on installing and running a testcloud virtual instance.
  2. Once SSH'ed into the virtual cloud instance, you can perform the tests below. NOTE: testcloud will work with both Fedora Cloud and Atomic images.


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
Basic QA:Testcase_base_system_logging
Final QA:Testcase_base_services_start
Final QA:Testcase_base_selinux
Final QA:Testcase_base_service_manipulation