From Fedora Project Wiki

(Result(s) for test(s): QA:Testcase_base_services_start filed via relval)
(Result(s) for test(s): QA:Testcase_base_service_manipulation filed via relval)
 
(One intermediate revision by the same user not shown)
Line 141: Line 141:
| Final
| Final
| [[QA:Testcase_base_selinux]]
| [[QA:Testcase_base_selinux]]
| {{result|pass|coconut|bot=true}}
| {{result|pass|coconut|bot=true}}{{result|pass|moonlight|bot=true}}
| {{result|none}}
| {{result|none}}
| {{result|none}}
| {{result|none}}
Line 147: Line 147:
| Final
| Final
| [[QA:Testcase_base_service_manipulation]]
| [[QA:Testcase_base_service_manipulation]]
| {{result|pass|coconut|bot=true}}
| {{result|pass|coconut|bot=true}}{{result|pass|moonlight|bot=true}}
| {{result|none}}
| {{result|none}}
| {{result|none}}
| {{result|none}}

Latest revision as of 07:49, 5 August 2021

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 20210804.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
Cloud_Base raw-xz 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
Cinnamon live Download
Container_Base docker Download Download Download Download Download
Container_Minimal_Base docker Download Download Download Download Download
Kinoite dvd-ostree Download Download Download
Python_Classroom vagrant-libvirt Download
Python_Classroom vagrant-virtualbox Download
Astronomy_KDE live Download
Comp_Neuro live Download
Games live Download
Python_Classroom live Download
Robotics 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
KDE raw-xz Download Download
Minimal raw-xz Download Download
Xfce raw-xz Download Download
SoaS raw-xz Download Download
Python_Classroom raw-xz Download Download

x86_64 hvm standard AMIs[edit]

Region AMI ID Direct launch link
ap-northeast-1 ami-0343263bd5afd41f5 Launch in EC2
ap-northeast-2 ami-0e16acba274b3a46e Launch in EC2
ap-south-1 ami-062be45bf606ee16f Launch in EC2
ap-southeast-1 ami-0e62a9ddde1b4b425 Launch in EC2
ap-southeast-2 ami-06f6555b0ff9d7331 Launch in EC2
ca-central-1 ami-0ffee32cf1b81614d Launch in EC2
eu-central-1 ami-034981e88906f64d7 Launch in EC2
eu-west-1 ami-01674323fd7c61b3d Launch in EC2
eu-west-2 ami-025a21ad0464bca97 Launch in EC2
sa-east-1 ami-09692461826d9e968 Launch in EC2
us-east-1 ami-0327ce8fccb20c88c Launch in EC2
us-east-2 ami-056f29dc454f804ab Launch in EC2
us-west-1 ami-00d7729cd2d02f810 Launch in EC2
us-west-2 ami-03bd3477da8690fde Launch in EC2

x86_64 hvm gp2 AMIs[edit]

Region AMI ID Direct launch link
ap-northeast-1 ami-0638cd134e48cbfb3 Launch in EC2
ap-northeast-2 ami-0f6ffffb57a6229da Launch in EC2
ap-south-1 ami-0e986c38e9d2221e8 Launch in EC2
ap-southeast-1 ami-03564529e4e86d566 Launch in EC2
ap-southeast-2 ami-00e442377cb5d9eac Launch in EC2
ca-central-1 ami-01f614beb85f77e47 Launch in EC2
eu-central-1 ami-03fd886d44d3337b5 Launch in EC2
eu-west-1 ami-014faa316a596544a Launch in EC2
eu-west-2 ami-03c22f3754e34bed7 Launch in EC2
sa-east-1 ami-01336ca75b7d23f1f Launch in EC2
us-east-1 ami-0ac31510d8143419b Launch in EC2
us-east-2 ami-0b02502db2df23870 Launch in EC2
us-west-1 ami-095be3346931be9b1 Launch in EC2
us-west-2 ami-0ccaec1097c8f6c06 Launch in EC2

arm64 hvm standard AMIs[edit]

Region AMI ID Direct launch link
ap-northeast-1 ami-0dab632f36d03f261 Launch in EC2
ap-northeast-2 ami-0613a3ce187753016 Launch in EC2
ap-south-1 ami-07f1cbcd8a9f4937a Launch in EC2
ap-southeast-1 ami-03de3513d22877917 Launch in EC2
ap-southeast-2 ami-07bc2f7981e938d1a Launch in EC2
ca-central-1 ami-01353f934705a5e06 Launch in EC2
eu-central-1 ami-0dc24d182159bb0e9 Launch in EC2
eu-west-1 ami-0205a13f9033710e2 Launch in EC2
eu-west-2 ami-07ae6b02788511f7a Launch in EC2
sa-east-1 ami-053d486e154e42b2e Launch in EC2
us-east-1 ami-013beb31deb5a7bfe Launch in EC2
us-east-2 ami-0fe0f194854b35324 Launch in EC2
us-west-1 ami-0c64c10438a2e7687 Launch in EC2
us-west-2 ami-0a9eb339504262ea8 Launch in EC2

arm64 hvm gp2 AMIs[edit]

Region AMI ID Direct launch link
ap-northeast-1 ami-0cc9d86783bd8a593 Launch in EC2
ap-northeast-2 ami-05164274da91f5b2d Launch in EC2
ap-south-1 ami-024e13108949800c3 Launch in EC2
ap-southeast-1 ami-05729d11fda0940d2 Launch in EC2
ap-southeast-2 ami-083191c11cb73afad Launch in EC2
ca-central-1 ami-0323b0681e2793ab8 Launch in EC2
eu-central-1 ami-0444757b542418b06 Launch in EC2
eu-west-1 ami-07d1f642817c377d2 Launch in EC2
eu-west-2 ami-028854ce0842beb45 Launch in EC2
sa-east-1 ami-03071ca6f744f3a7d Launch in EC2
us-east-1 ami-07cc2181f39d7f1fa Launch in EC2
us-east-2 ami-0f8a4b8d4d49bceb6 Launch in EC2
us-west-1 ami-0261738a6b73d669c Launch in EC2
us-west-2 ami-057a1394338168274 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 20210804.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
Bot Pass pass moonlight
Basic QA:Testcase_base_system_logging
Bot Pass pass coconut
none
none
Bot Pass pass moonlight
Basic QA:Testcase_base_update_cli
Bot Pass pass coconut
none
none
Bot Pass pass moonlight
Basic / Beta QA:Testcase_package_install_remove
Bot Pass pass coconut
none
none
Bot Pass pass moonlight
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
Bot Pass pass moonlight
Final QA:Testcase_base_selinux
Bot Pass pass coconut
none
none
Bot Pass pass moonlight
Final QA:Testcase_base_service_manipulation
Bot Pass pass coconut
none
none
Bot Pass pass moonlight


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