From Fedora Project Wiki

Important.png
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 20200109.n.0 nightly compose.

Which tests to run[edit]

Note.png
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 ppc64le s390x x86_64
Everything boot Download Download Download Download Download
Workstation live Download
Server dvd Download Download Download Download Download
Server boot Download 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
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-0ba331e952af5fda5 Launch in EC2
ap-northeast-2 ami-0a87a439bdb16d810 Launch in EC2
ap-south-1 ami-071d84d49c08c8533 Launch in EC2
ap-southeast-1 ami-0b97dcf0c9f598aa2 Launch in EC2
ap-southeast-2 ami-05e4f1cc084882b17 Launch in EC2
ca-central-1 ami-0012593bc611675e0 Launch in EC2
eu-central-1 ami-05e97431eac28cd34 Launch in EC2
eu-west-1 ami-09ee92ed4a802b2c6 Launch in EC2
eu-west-2 ami-0f0b30588aa0e9be0 Launch in EC2
sa-east-1 ami-00579d6a70714da15 Launch in EC2
us-east-1 ami-0f031efd9b661730a Launch in EC2
us-east-2 ami-0e22d042c2f5bd211 Launch in EC2
us-west-1 ami-00f33646317bac7a7 Launch in EC2
us-west-2 ami-0a2111b54c7258468 Launch in EC2

x86_64 hvm gp2 AMIs[edit]

Region AMI ID Direct launch link
ap-northeast-1 ami-08be98866c6e84525 Launch in EC2
ap-northeast-2 ami-05a1ca6f93f704274 Launch in EC2
ap-south-1 ami-096a1b1f859f3c60e Launch in EC2
ap-southeast-1 ami-0a4b8a50bfc39dce0 Launch in EC2
ap-southeast-2 ami-04d862d9b96dcf30d Launch in EC2
ca-central-1 ami-0808dd6aa4aeaf51a Launch in EC2
eu-central-1 ami-0e4e8e89f3a9c76ae Launch in EC2
eu-west-1 ami-0fd8a0b212c1f1ac4 Launch in EC2
eu-west-2 ami-058c5805b3092bbfe Launch in EC2
sa-east-1 ami-056abf72610d449a4 Launch in EC2
us-east-1 ami-03b473c49a18274d7 Launch in EC2
us-east-2 ami-08b6831257ea11d3e Launch in EC2
us-west-1 ami-026c36a23c71d2347 Launch in EC2
us-west-2 ami-035c60a83eba53e38 Launch in EC2

arm64 hvm standard AMIs[edit]

Region AMI ID Direct launch link
ap-northeast-1 ami-099db4dbb79a8d524 Launch in EC2
ap-northeast-2 ami-0bf67a022a1589f6e Launch in EC2
ap-south-1 ami-07a4c848e6532b1e0 Launch in EC2
ap-southeast-1 ami-0c93a33fecfb7007c Launch in EC2
ap-southeast-2 ami-0d5531128825df865 Launch in EC2
ca-central-1 ami-0379b2fd70fb52f33 Launch in EC2
eu-central-1 ami-002dec252339b2735 Launch in EC2
eu-west-1 ami-0213bfca2f96bb60e Launch in EC2
eu-west-2 ami-04d40d5db7252174b Launch in EC2
sa-east-1 ami-04944e32f2138cfd8 Launch in EC2
us-east-1 ami-0e3c119cb35521643 Launch in EC2
us-east-2 ami-088a2108d4ba421a7 Launch in EC2
us-west-1 ami-0121800da9d140fcc Launch in EC2
us-west-2 ami-052338a5f8dd635da Launch in EC2

arm64 hvm gp2 AMIs[edit]

Region AMI ID Direct launch link
ap-northeast-1 ami-08b8b22ce91149c38 Launch in EC2
ap-northeast-2 ami-088abff6796a3e8da Launch in EC2
ap-south-1 ami-0cf363ab15a4a3961 Launch in EC2
ap-southeast-1 ami-04a7ec86d22edd3fe Launch in EC2
ap-southeast-2 ami-0363ec6c1948b5995 Launch in EC2
ca-central-1 ami-048f1b539c0c0dd20 Launch in EC2
eu-central-1 ami-03aac4ad8d2749997 Launch in EC2
eu-west-1 ami-04651187f274bce18 Launch in EC2
eu-west-2 ami-05ec7bca7f419a5fa Launch in EC2
sa-east-1 ami-0a0b7aee12d4cae92 Launch in EC2
us-east-1 ami-07ba9d1643d421f73 Launch in EC2
us-east-2 ami-0f39f48c3b4ef9814 Launch in EC2
us-west-1 ami-01896f9ead12a1ce6 Launch in EC2
us-west-2 ami-0686e5fbe884f359f 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.

Important.png
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.
Note.png
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 20200109.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.

Key[edit]

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
none
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
{{result|fail|jlaska|XYZ|ZXY}}
Warning warn rhe
[1]
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 http://cloud.fedoraproject.org/. 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)

Openstack

  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 http://cloud.fedoraproject.org/ 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.

x86_64[edit]

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


aarch64[edit]

Milestone Test Case Local EC2 (KVM) Openstack
Basic QA:Testcase_base_startup
none
none
none
Basic QA:Testcase_base_system_logging
none
none
none
Final QA:Testcase_base_services_start
none
none
none
Final QA:Testcase_base_selinux
none
none
none
Final QA:Testcase_base_service_manipulation
none
none
none