From Fedora Project Wiki

(Result(s) for test(s): QA:Testcase_base_reboot_unmount filed via relval)
(Result(s) for test(s): QA:Testcase_base_startup filed via relval)
 
(2 intermediate revisions by the same user not shown)
Line 15: Line 15:
| Basic
| Basic
| [[QA:Testcase_base_startup]]
| [[QA:Testcase_base_startup]]
| {{result|none}}
| {{result|pass|coconut|bot=true}}
| {{result|none}}
| {{result|none}}
| {{result|none}}
| {{result|none}}
Line 36: Line 36:
| 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}}
Line 78: Line 78:
| Final
| Final
| [[QA:Testcase_base_service_manipulation]]
| [[QA:Testcase_base_service_manipulation]]
| {{result|none}}
| {{result|pass|coconut|bot=true}}
| {{result|none}}
| {{result|none}}
| {{result|none}}
| {{result|none}}

Latest revision as of 16:16, 21 June 2020

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 33 20200620.n.1 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 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 x86_64
Everything boot Download Download Download Download
Workstation live Download Download
Server dvd 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
Mate live Download
Cinnamon 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
Comp_Neuro live Download
Jam_KDE 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
Mate raw-xz Download
LXDE raw-xz Download
Silverblue dvd-ostree Download
LXQt raw-xz Download

x86_64 hvm standard AMIs[edit]

Region AMI ID Direct launch link
ap-northeast-1 ami-06447dd4324143d62 Launch in EC2
ap-northeast-2 ami-0b14a9e5210366f9b Launch in EC2
ap-south-1 ami-03ad38df5cbf161ac Launch in EC2
ap-southeast-1 ami-07aa853e0eb9d4006 Launch in EC2
ap-southeast-2 ami-0d7a7f0152356265d Launch in EC2
ca-central-1 ami-0cf657b321891f954 Launch in EC2
eu-central-1 ami-0a580bfed7b006780 Launch in EC2
eu-west-1 ami-0797a1c4b4686513a Launch in EC2
eu-west-2 ami-049b89a6064128bae Launch in EC2
sa-east-1 ami-02dd1d0113cb03e56 Launch in EC2
us-east-1 ami-05336596882d6d8ed Launch in EC2
us-east-2 ami-04eb34cb0a6626196 Launch in EC2
us-west-1 ami-0d5ee6192c7d16123 Launch in EC2
us-west-2 ami-01bc2911325aba12c Launch in EC2

x86_64 hvm gp2 AMIs[edit]

Region AMI ID Direct launch link
ap-northeast-1 ami-0bcfe81c8a3f91ab7 Launch in EC2
ap-northeast-2 ami-0fab5f508706b8aff Launch in EC2
ap-south-1 ami-03efe85413b9f2db0 Launch in EC2
ap-southeast-1 ami-0389bb6f22ff5c018 Launch in EC2
ap-southeast-2 ami-092302a8cc8976374 Launch in EC2
ca-central-1 ami-0a8b01c81fa034275 Launch in EC2
eu-central-1 ami-04d221808ef1944e8 Launch in EC2
eu-west-1 ami-0cfa5c0acd699e56a Launch in EC2
eu-west-2 ami-069df1b29e11ba491 Launch in EC2
sa-east-1 ami-07cc353173a2ec796 Launch in EC2
us-east-1 ami-09208c21984b0017e Launch in EC2
us-east-2 ami-0bb42eca20ecbbbb0 Launch in EC2
us-west-1 ami-08b6226c841c12ebf Launch in EC2
us-west-2 ami-0649cdfe7d6086536 Launch in EC2

arm64 hvm standard AMIs[edit]

Region AMI ID Direct launch link
ap-northeast-1 ami-036fe03466dc90865 Launch in EC2
ap-northeast-2 ami-0b4abad735d130135 Launch in EC2
ap-south-1 ami-01357ab8aea2c6c2c Launch in EC2
ap-southeast-1 ami-07bb42fad90ff1ef4 Launch in EC2
ap-southeast-2 ami-0fa7b36c300595f10 Launch in EC2
ca-central-1 ami-09fc4661f8d9ec3f4 Launch in EC2
eu-central-1 ami-09577d4ac04bdff30 Launch in EC2
eu-west-1 ami-0344fc18fcecc2eb8 Launch in EC2
eu-west-2 ami-01d3f072be77bff3e Launch in EC2
sa-east-1 ami-023dc8295d3f60c8a Launch in EC2
us-east-1 ami-0ccc12c740c1f007c Launch in EC2
us-east-2 ami-086bc899c5988a883 Launch in EC2
us-west-1 ami-0843df4cd608025d3 Launch in EC2
us-west-2 ami-0458f8ec0bfb619d9 Launch in EC2

arm64 hvm gp2 AMIs[edit]

Region AMI ID Direct launch link
ap-northeast-1 ami-08d4bdb82010ddf7b Launch in EC2
ap-northeast-2 ami-07504f759ef5c4b09 Launch in EC2
ap-south-1 ami-0c08fa6744010223d Launch in EC2
ap-southeast-1 ami-0ee8f7091aab98cec Launch in EC2
ap-southeast-2 ami-019cb6b4b05726a1c Launch in EC2
ca-central-1 ami-06392d17e6a5e3b67 Launch in EC2
eu-central-1 ami-0c62ee53f34e731c3 Launch in EC2
eu-west-1 ami-058af0a1885fdd287 Launch in EC2
eu-west-2 ami-075235ed2d6b9e551 Launch in EC2
sa-east-1 ami-0e8965fff8b4ebf71 Launch in EC2
us-east-1 ami-0cbe209312b721a3b Launch in EC2
us-east-2 ami-0f45fa160ef6307ee Launch in EC2
us-west-1 ami-04cf58814f08f7ebc Launch in EC2
us-west-2 ami-041e28dc32f67cf1d 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 33 Rawhide 20200620.n.1 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
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[edit]

Milestone Test Case Local EC2 (KVM) Openstack
Basic QA:Testcase_base_startup
none
none
none
Basic QA:Testcase_base_reboot_unmount
none
none
none
Basic QA:Testcase_base_system_logging
none
none
none
Basic QA:Testcase_base_update_cli
none
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
none
none
none
Final QA:Testcase_base_selinux
none
none
none
Final QA:Testcase_base_service_manipulation
none
none
none