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 35 20210506.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 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 tar-gz Download
Cloud_Base vagrant-libvirt Download
Cloud_Base vagrant-virtualbox Download
KDE live Download Download
Xfce live Download
SoaS live Download
Mate live Download
Cinnamon live Download
LXDE live Download
Container_Base docker Download Download Download Download Download
Container_Minimal_Base docker Download Download Download Download Download
Python_Classroom vagrant-libvirt Download
Python_Classroom vagrant-virtualbox Download
Scientific vagrant-libvirt Download
Scientific vagrant-virtualbox Download
Comp_Neuro live Download
Design_suite live Download
Games live Download
Jam_KDE live Download
Python_Classroom live Download
Scientific_KDE live Download
Security live Download
Silverblue dvd-ostree Download Download Download
LXQt live Download
i3 live Download
Workstation raw-xz Download Download
Server raw-xz Download Download
Minimal raw-xz Download Download
Xfce raw-xz Download Download

x86_64 hvm standard AMIs[edit]

Region AMI ID Direct launch link
ap-northeast-1 ami-0edd280cea51e2df9 Launch in EC2
ap-northeast-2 ami-0cdc6ed1749466861 Launch in EC2
ap-south-1 ami-0f83dbbcfa3c48bea Launch in EC2
ap-southeast-1 ami-05599ce480d82fdb1 Launch in EC2
ap-southeast-2 ami-0b5a08cd1275d905a Launch in EC2
ca-central-1 ami-045d9334f0b379cd6 Launch in EC2
eu-central-1 ami-04f565eeb6869534f Launch in EC2
eu-west-1 ami-0ea624d533eb5dc20 Launch in EC2
eu-west-2 ami-029b45fad97f7d88e Launch in EC2
sa-east-1 ami-080b5a7edf6963243 Launch in EC2
us-east-1 ami-09653d393517c1ccf Launch in EC2
us-east-2 ami-0ba37710e6e7a2b0f Launch in EC2
us-west-1 ami-06c0f1fa843ffe919 Launch in EC2
us-west-2 ami-0edab964ed8df1477 Launch in EC2

x86_64 hvm gp2 AMIs[edit]

Region AMI ID Direct launch link
ap-northeast-1 ami-0b124bcdc35e5291e Launch in EC2
ap-northeast-2 ami-0c77ec04c82067450 Launch in EC2
ap-south-1 ami-00b5c860dc491e59a Launch in EC2
ap-southeast-1 ami-02b11cf09428b0433 Launch in EC2
ap-southeast-2 ami-08b4babb2d5d27cf4 Launch in EC2
ca-central-1 ami-045f0e8e86da61056 Launch in EC2
eu-central-1 ami-031178b8f24135be5 Launch in EC2
eu-west-1 ami-0b53ae77b4d00fdb9 Launch in EC2
eu-west-2 ami-07e3ddaf31b47e3fe Launch in EC2
sa-east-1 ami-0b6f35f9f2bca1c42 Launch in EC2
us-east-1 ami-0d580b18a8146fa62 Launch in EC2
us-east-2 ami-07b72108d16e45192 Launch in EC2
us-west-1 ami-093dbced4acb756d8 Launch in EC2
us-west-2 ami-010a062c3e1a7cf55 Launch in EC2

arm64 hvm standard AMIs[edit]

Region AMI ID Direct launch link
ap-northeast-1 ami-016f21a4e889d4219 Launch in EC2
ap-northeast-2 ami-08f921dc9e27fbbc2 Launch in EC2
ap-south-1 ami-0a0f0f563bfad7667 Launch in EC2
ap-southeast-1 ami-0389216ff833b12ea Launch in EC2
ap-southeast-2 ami-0c861e06083f072ee Launch in EC2
ca-central-1 ami-07b5e251603fc0ef6 Launch in EC2
eu-central-1 ami-0d343a627d4fd9066 Launch in EC2
eu-west-1 ami-00c1e549514042e14 Launch in EC2
eu-west-2 ami-0f404a7ddde9d2ccb Launch in EC2
sa-east-1 ami-01b509c2ad8a5e44a Launch in EC2
us-east-1 ami-0d02ecb45d251a961 Launch in EC2
us-east-2 ami-023fc6fb00ebad53a Launch in EC2
us-west-1 ami-069ecf1532cedfc5e Launch in EC2
us-west-2 ami-01e926dc233e1c0d5 Launch in EC2

arm64 hvm gp2 AMIs[edit]

Region AMI ID Direct launch link
ap-northeast-1 ami-0b2854518d4a33e99 Launch in EC2
ap-northeast-2 ami-00bcbceb8cef1619b Launch in EC2
ap-south-1 ami-0cdc338b7547e4a34 Launch in EC2
ap-southeast-1 ami-012267cf0f8db7ea2 Launch in EC2
ap-southeast-2 ami-0e7c5d6bee7e5e5cb Launch in EC2
ca-central-1 ami-0c2f1f3ebc729927a Launch in EC2
eu-central-1 ami-079679bda976b611e Launch in EC2
eu-west-1 ami-0e563202469b752f8 Launch in EC2
eu-west-2 ami-04ccc55a460ca8985 Launch in EC2
sa-east-1 ami-08380ac06b7535a01 Launch in EC2
us-east-1 ami-0355539091f7e1a1f Launch in EC2
us-east-2 ami-0e231bc3a86ecef02 Launch in EC2
us-west-1 ami-012a7b0d729a817e8 Launch in EC2
us-west-2 ami-0f586da1d9b5b85f2 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 35 Rawhide 20210506.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}}
Fail fail pboy [1] [2]
Failed - Same issue with LVM again
  1. RHBZ #2246871
  2. RHBZ #'2244305
{{result|fail|pboy|2246871|2244305}}
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

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.

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_reboot_unmount
Bot Pass pass coconut
none
none
none
Basic QA:Testcase_base_system_logging
Bot Pass pass coconut
none
none
none
Basic QA:Testcase_base_update_cli
Bot Pass pass coconut
none
none
none
Basic / Beta QA:Testcase_package_install_remove
Bot Pass pass coconut
none
none
none
Basic / Final QA:Testcase_base_artwork_release_identification
none
none
none
none
Final QA:Testcase_base_edition_self_identification
none
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
Bot Pass pass coconut
none
none
Basic QA:Testcase_base_reboot_unmount
Bot Pass pass coconut
none
none
Basic QA:Testcase_base_system_logging
Bot Pass pass coconut
none
none
Basic QA:Testcase_base_update_cli
Bot Pass pass coconut
none
none
Basic / Beta QA:Testcase_package_install_remove
Bot Pass pass coconut
none
none
Basic / Final QA:Testcase_base_artwork_release_identification
none
none
none
Final QA:Testcase_base_edition_self_identification
none
none
none
Final QA:Testcase_base_services_start
Bot Pass pass coconut
none
none
Final QA:Testcase_base_selinux
Bot Pass pass coconut
none
none
Final QA:Testcase_base_service_manipulation
Bot Pass pass coconut
none
none