From Fedora Project Wiki

(→‎x86_64: sshd service starts even if disabled. Test passes when substituting chronyd for sshd.)
Line 46: Line 46:
 
| {{result|none}}
 
| {{result|none}}
 
| {{result|none}}
 
| {{result|none}}
| {{result|none}}
+
| {{result|warn|cyberpear}} <ref>sshd service starts even if disabled.  Test passes when substituting chronyd for sshd.</ref>
 
|-
 
|-
 
|}
 
|}

Revision as of 18:39, 14 April 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 32 RC 1.2 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 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
Silverblue dvd-ostree Download Download 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

Region AMI ID Direct launch link
ap-northeast-1 ami-0b2b6a22fed99c0fb Launch in EC2
ap-northeast-2 ami-0ab279b61156d3168 Launch in EC2
ap-south-1 ami-06990fecdc7cf747b Launch in EC2
ap-southeast-1 ami-0d4106837bda0280b Launch in EC2
ap-southeast-2 ami-01c9bd1c6c1e17b47 Launch in EC2
ca-central-1 ami-05574ae6a07b1ec29 Launch in EC2
eu-central-1 ami-0482cfd668ce3d105 Launch in EC2
eu-west-1 ami-0314dbf6c2c355562 Launch in EC2
eu-west-2 ami-0716c278d65f6ebcc Launch in EC2
sa-east-1 ami-0c5c30833debc5464 Launch in EC2
us-east-1 ami-09d008de46e1a86be Launch in EC2
us-east-2 ami-00823b3537340864a Launch in EC2
us-west-1 ami-06a3fb45e0368e9ea Launch in EC2
us-west-2 ami-012bd5d719d86477e Launch in EC2

x86_64 hvm gp2 AMIs

Region AMI ID Direct launch link
ap-northeast-1 ami-0d7e6eb3d85cf9dad Launch in EC2
ap-northeast-2 ami-0064fdfc148cae948 Launch in EC2
ap-south-1 ami-09cc3db6659cd3557 Launch in EC2
ap-southeast-1 ami-0ec48dbaf1ccf4e0c Launch in EC2
ap-southeast-2 ami-0a30eb526e5706f7d Launch in EC2
ca-central-1 ami-057fb86b0d7ef3fef Launch in EC2
eu-central-1 ami-03d1213ef6d81d894 Launch in EC2
eu-west-1 ami-028bdd35530a9dac3 Launch in EC2
eu-west-2 ami-0e46dcfd0e27bc49c Launch in EC2
sa-east-1 ami-0a9544e54dfc3111e Launch in EC2
us-east-1 ami-0daa0298a7f58930d Launch in EC2
us-east-2 ami-0de247b4b1a2dd6d9 Launch in EC2
us-west-1 ami-0d81479134d435f58 Launch in EC2
us-west-2 ami-05db3d5a6a9953264 Launch in EC2

arm64 hvm standard AMIs

Region AMI ID Direct launch link
ap-northeast-1 ami-0cb6ea5446cbd5663 Launch in EC2
ap-northeast-2 ami-0dd5854d8423d2573 Launch in EC2
ap-south-1 ami-0381c0014173abd2c Launch in EC2
ap-southeast-1 ami-0a1dfc7769ad4b6aa Launch in EC2
ap-southeast-2 ami-07910f3f7df0e6861 Launch in EC2
ca-central-1 ami-0d866df95260300f9 Launch in EC2
eu-central-1 ami-0f44538e3afe46a94 Launch in EC2
eu-west-1 ami-00529ce435ce173a5 Launch in EC2
eu-west-2 ami-0338f928a58bc9868 Launch in EC2
sa-east-1 ami-0834771ff1f8e6de1 Launch in EC2
us-east-1 ami-045a73bde073d2921 Launch in EC2
us-east-2 ami-03ea7efcf9e62d61e Launch in EC2
us-west-1 ami-0f55f92a43450cc5d Launch in EC2
us-west-2 ami-060d60aebf192a890 Launch in EC2

arm64 hvm gp2 AMIs

Region AMI ID Direct launch link
ap-northeast-1 ami-094572c1978ab4556 Launch in EC2
ap-northeast-2 ami-00e81e6d23a332f9e Launch in EC2
ap-south-1 ami-0f734aa2b5f73eeb5 Launch in EC2
ap-southeast-1 ami-09bff65ee595be8be Launch in EC2
ap-southeast-2 ami-07bda9b6a88d2fa7c Launch in EC2
ca-central-1 ami-05a28df9fc4294909 Launch in EC2
eu-central-1 ami-015714dbfe0080f8e Launch in EC2
eu-west-1 ami-047f45997830a8fa2 Launch in EC2
eu-west-2 ami-07a9571bceba62e08 Launch in EC2
sa-east-1 ami-09d6be6d4e3ccf258 Launch in EC2
us-east-1 ami-0aef8fcbcd3ce2223 Launch in EC2
us-east-2 ami-09a007c73b1fd97c2 Launch in EC2
us-west-1 ami-0e73517ffbe73221d Launch in EC2
us-west-2 ami-0cf94bf16cad9877c 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 32 RC 1.2 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}}
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
Bot Pass pass coconut
none
none
Pass pass cyberpear
Basic QA:Testcase_base_system_logging
Bot Pass pass coconut
none
none
Pass pass cyberpear
Final QA:Testcase_base_services_start
Bot Pass pass coconut
none
none
Pass pass cyberpear
Final QA:Testcase_base_selinux
Bot Pass pass coconut
none
none
Pass pass cyberpear
Final QA:Testcase_base_service_manipulation
Bot Pass pass coconut
none
none
Warning warn cyberpear
[1]
  1. sshd service starts even if disabled. Test passes when substituting chronyd for sshd.

aarch64

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