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 20200225.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 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
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-0b51c24a829cabe5f Launch in EC2
ap-northeast-2 ami-0c7a677c114b015e6 Launch in EC2
ap-south-1 ami-03d517c3c8c4b19de Launch in EC2
ap-southeast-1 ami-0801d70643053e502 Launch in EC2
ap-southeast-2 ami-0b5a22fa092141355 Launch in EC2
ca-central-1 ami-0d7b199a95aefc5ed Launch in EC2
eu-central-1 ami-0f81b0f9f007423af Launch in EC2
eu-west-1 ami-0938c63e203476267 Launch in EC2
eu-west-2 ami-07bc7e467f97a0650 Launch in EC2
sa-east-1 ami-059776276ecf8e1ac Launch in EC2
us-east-1 ami-04c38b94aac6a0737 Launch in EC2
us-east-2 ami-0fbcc0c01b551143d Launch in EC2
us-west-1 ami-07e76ec6c81cfe171 Launch in EC2
us-west-2 ami-043530845c74a7756 Launch in EC2

x86_64 hvm gp2 AMIs[edit]

Region AMI ID Direct launch link
ap-northeast-1 ami-0fa7e7aacbf3ac2b5 Launch in EC2
ap-northeast-2 ami-0ed31330c05c34999 Launch in EC2
ap-south-1 ami-082e6ea572d605d5a Launch in EC2
ap-southeast-1 ami-0d3326a27816b301e Launch in EC2
ap-southeast-2 ami-0f3f29e2e5c5b5825 Launch in EC2
ca-central-1 ami-0e38ebe35deb95d96 Launch in EC2
eu-central-1 ami-0f040c1b1fc81ff77 Launch in EC2
eu-west-1 ami-027f93443b1036ab3 Launch in EC2
eu-west-2 ami-011658492abed7421 Launch in EC2
sa-east-1 ami-07f851d8354f2307b Launch in EC2
us-east-1 ami-003ce828b9f9a8d1f Launch in EC2
us-east-2 ami-0510df0ba48c2e6e9 Launch in EC2
us-west-1 ami-0697c456214067fc3 Launch in EC2
us-west-2 ami-0249c8470071ffd7b Launch in EC2

arm64 hvm standard AMIs[edit]

Region AMI ID Direct launch link
ap-northeast-1 ami-09364e2e2c835d117 Launch in EC2
ap-northeast-2 ami-0b5414e5b9c5da66e Launch in EC2
ap-south-1 ami-0c19afd0a3a32ac54 Launch in EC2
ap-southeast-1 ami-03bfa58faf3cfc9a7 Launch in EC2
ap-southeast-2 ami-01655a4629f050cae Launch in EC2
ca-central-1 ami-09f97643145a8899a Launch in EC2
eu-central-1 ami-01ff70b3d5f167a95 Launch in EC2
eu-west-1 ami-00e18c5e2202c9119 Launch in EC2
eu-west-2 ami-0a1dba9bba94b9339 Launch in EC2
sa-east-1 ami-047e1cf3a3edb5500 Launch in EC2
us-east-1 ami-0aed1d986842bcb9a Launch in EC2
us-east-2 ami-0dfb4dd2e03f3a01f Launch in EC2
us-west-1 ami-0a7e646418ccab3f4 Launch in EC2
us-west-2 ami-06e0ee1692fdac0cf Launch in EC2

arm64 hvm gp2 AMIs[edit]

Region AMI ID Direct launch link
ap-northeast-1 ami-053eb9d7b70c1df11 Launch in EC2
ap-northeast-2 ami-05b546ab58a61073c Launch in EC2
ap-south-1 ami-0c4bb4c64b37ee996 Launch in EC2
ap-southeast-1 ami-065081e20eb1a94a9 Launch in EC2
ap-southeast-2 ami-0aed085c7cef12f65 Launch in EC2
ca-central-1 ami-03ac4e6a51ad8f6e9 Launch in EC2
eu-central-1 ami-0adf2f37642371306 Launch in EC2
eu-west-1 ami-05eadeb8bd1e2cd66 Launch in EC2
eu-west-2 ami-0a176ae42fe8ae62a Launch in EC2
sa-east-1 ami-0280d22ee7fc0b1e7 Launch in EC2
us-east-1 ami-0c488861491336f30 Launch in EC2
us-east-2 ami-091518f2aadad66ca Launch in EC2
us-west-1 ami-03d4ca44da0efdf1f Launch in EC2
us-west-2 ami-0741ec189d0aaa7b4 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 Branched 20200225.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