From Fedora Project Wiki

(Result(s) for test(s): QA:Testcase_base_service_manipulation filed via relval)
(Result(s) for test(s): QA:Testcase_base_update_cli filed via relval)
Line 111: Line 111:
| Basic
| Basic
| [[QA:Testcase_base_update_cli]]
| [[QA:Testcase_base_update_cli]]
| {{result|none}}
| {{result|pass|coconut|bot=true}}
| {{result|none}}
| {{result|none}}
| {{result|none}}
| {{result|none}}

Revision as of 11:43, 13 February 2021

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 34 20210213.n.0 nightly compose.

Which tests to run

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 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

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

Image aarch64 armhfp ppc64le x86_64
Everything boot Download Download Download
Workstation live Download Download Download
Server dvd Download Download Download
Server boot Download Download Download
Cloud_Base qcow2 Download Download
Cloud_Base raw-xz Download Download
Cloud_Base tar-gz Download
Cloud_Base vagrant-libvirt Download
Cloud_Base vagrant-virtualbox Download
KDE live Download Download
SoaS live Download
Cinnamon live Download
LXDE live Download
Container_Base docker Download Download
Container_Minimal_Base docker Download Download
Python_Classroom vagrant-libvirt Download
Python_Classroom vagrant-virtualbox Download
Comp_Neuro live Download
Design_suite live Download
Python_Classroom live Download
Robotics live Download
Silverblue dvd-ostree Download Download
Workstation raw-xz Download
Server raw-xz Download
KDE raw-xz Download
Minimal raw-xz Download
SoaS raw-xz Download
Mate raw-xz Download
LXDE raw-xz Download
Python_Classroom raw-xz Download
Server_Appliance raw-xz Download
KDE_Appliance raw-xz Download
LXQt raw-xz Download
Minimal_Appliance raw-xz Download
Workstation_Appliance raw-xz Download

x86_64 hvm standard AMIs

Region AMI ID Direct launch link
ap-northeast-1 ami-0850bf90e2d3f8b83 Launch in EC2
ap-northeast-2 ami-095cc3735eef146d3 Launch in EC2
ap-south-1 ami-077f6db97f31cb57f Launch in EC2
ap-southeast-1 ami-00fadf98159d6004b Launch in EC2
ap-southeast-2 ami-0a259b3571b6f3164 Launch in EC2
ca-central-1 ami-09c25dda61369e000 Launch in EC2
eu-central-1 ami-0e436f91cee09e696 Launch in EC2
eu-west-1 ami-01adab0cb57ca70a8 Launch in EC2
eu-west-2 ami-09086970ce7c693d3 Launch in EC2
sa-east-1 ami-0120f14ef091d93c3 Launch in EC2
us-east-1 ami-0a001ee9ed5fce2e0 Launch in EC2
us-east-2 ami-08903e21652d8c025 Launch in EC2
us-west-1 ami-0d72c9eaaf8f59512 Launch in EC2
us-west-2 ami-029042a632263c807 Launch in EC2

x86_64 hvm gp2 AMIs

Region AMI ID Direct launch link
ap-northeast-1 ami-09a20f9f3766b72ac Launch in EC2
ap-northeast-2 ami-0e3f5fc4327faa7d7 Launch in EC2
ap-south-1 ami-0123b7342d33e3674 Launch in EC2
ap-southeast-1 ami-03303561677fffb56 Launch in EC2
ap-southeast-2 ami-0f7e9d966fb080362 Launch in EC2
ca-central-1 ami-07e146e4f82a00844 Launch in EC2
eu-central-1 ami-0ca454aa07e11d989 Launch in EC2
eu-west-1 ami-0e5d61b55a40388be Launch in EC2
eu-west-2 ami-0075a18e004fe99fb Launch in EC2
sa-east-1 ami-095741558cf9f6e4e Launch in EC2
us-east-1 ami-04406eed5344e44a4 Launch in EC2
us-east-2 ami-0031a3a73cc8386aa Launch in EC2
us-west-1 ami-0d95d49caaf6ec806 Launch in EC2
us-west-2 ami-03b90f08edd7d5f7a Launch in EC2

arm64 hvm standard AMIs

Region AMI ID Direct launch link
ap-northeast-1 ami-017941b6d07d5800e Launch in EC2
ap-northeast-2 ami-0028efcf59bf136f7 Launch in EC2
ap-south-1 ami-0d4c93c523e6f0a52 Launch in EC2
ap-southeast-1 ami-087195fd518f0df83 Launch in EC2
ap-southeast-2 ami-0b0f7d1c2f55ed2b8 Launch in EC2
ca-central-1 ami-0b48745d7b60261f9 Launch in EC2
eu-central-1 ami-06ff5b853663b2bea Launch in EC2
eu-west-1 ami-031adff85f9fc0705 Launch in EC2
eu-west-2 ami-081784e9afc4ec91a Launch in EC2
sa-east-1 ami-01683afa390de2cdc Launch in EC2
us-east-1 ami-05a09b085663ae52d Launch in EC2
us-east-2 ami-01f25988f0aea830e Launch in EC2
us-west-1 ami-08a0424ac51f5d9b9 Launch in EC2
us-west-2 ami-00ea8edca7a56a253 Launch in EC2

arm64 hvm gp2 AMIs

Region AMI ID Direct launch link
ap-northeast-1 ami-0945207d1c8a0b1c5 Launch in EC2
ap-northeast-2 ami-0d0de312221485e05 Launch in EC2
ap-south-1 ami-0f705fbdf97bb43be Launch in EC2
ap-southeast-1 ami-01b8ac6e9a92ca3eb Launch in EC2
ap-southeast-2 ami-00ff63c96824dc4b9 Launch in EC2
ca-central-1 ami-08bbf60429c818c69 Launch in EC2
eu-central-1 ami-0585488c730af5030 Launch in EC2
eu-west-1 ami-0e3608a7e1afb7a71 Launch in EC2
eu-west-2 ami-0f764bbf5cdf3647f Launch in EC2
sa-east-1 ami-0a3fee9005c5eaf10 Launch in EC2
us-east-1 ami-0ea6102a0eef59a81 Launch in EC2
us-east-2 ami-0be66a4e84d01e8e1 Launch in EC2
us-west-1 ami-0664904d55abe8c36 Launch in EC2
us-west-2 ami-0256a5bbb94e14d23 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

The Test Results:Fedora 34 Branched 20210213.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

  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

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

Cloud Provider Setup

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

Milestone Test Case Local EC2 (KVM) EC2 (Xen) Openstack
Basic QA:Testcase_base_startup
none
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
none
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

Milestone Test Case Local EC2 (KVM) Openstack
Basic QA:Testcase_base_startup
none
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
none
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
none
none
none