From Fedora Project Wiki

Revision as of 00:17, 16 April 2020 by Cyberpear (talk | contribs) (→‎x86_64: couple of warnings, but everything passes)

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.3 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
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-077c4a1a751d4563b Launch in EC2
ap-northeast-2 ami-0d721a56309bb1f63 Launch in EC2
ap-south-1 ami-0b48d60fe77c11ce9 Launch in EC2
ap-southeast-1 ami-022f463ddb4097aa3 Launch in EC2
ap-southeast-2 ami-0ae7491757c9f8f48 Launch in EC2
ca-central-1 ami-01c4060605c1b2200 Launch in EC2
eu-central-1 ami-0b0df7071df68c65d Launch in EC2
eu-west-1 ami-0b1283ae0d1b7927f Launch in EC2
eu-west-2 ami-0556e8ab675119ffe Launch in EC2
sa-east-1 ami-0a6aaca25b6d229bc Launch in EC2
us-east-1 ami-0b6fb2f8c0a3244cd Launch in EC2
us-east-2 ami-0f9238eab0f31b3c2 Launch in EC2
us-west-1 ami-0f1385da3a9564030 Launch in EC2
us-west-2 ami-06810d4f95850a349 Launch in EC2

x86_64 hvm gp2 AMIs

Region AMI ID Direct launch link
ap-northeast-1 ami-0953690841e86c4d1 Launch in EC2
ap-northeast-2 ami-06cb889e4ef68d91d Launch in EC2
ap-south-1 ami-0fb04a73f1fd1f2e1 Launch in EC2
ap-southeast-1 ami-0509b672f46e88aaf Launch in EC2
ap-southeast-2 ami-012f126b663eaf1a9 Launch in EC2
ca-central-1 ami-027774d7a4a9158be Launch in EC2
eu-central-1 ami-08187340abfd8df98 Launch in EC2
eu-west-1 ami-01d6773360d48dd55 Launch in EC2
eu-west-2 ami-0024c659643e3af72 Launch in EC2
sa-east-1 ami-0a36a76e0eda36b5a Launch in EC2
us-east-1 ami-0061ee85a95862bef Launch in EC2
us-east-2 ami-0d2bda053d12b10d1 Launch in EC2
us-west-1 ami-0c31c0d9be9a788f2 Launch in EC2
us-west-2 ami-0f5ed4ff9a69cfff7 Launch in EC2

arm64 hvm standard AMIs

Region AMI ID Direct launch link
ap-northeast-1 ami-0290da98fc05ae9b4 Launch in EC2
ap-northeast-2 ami-0eb121b4a439753a6 Launch in EC2
ap-south-1 ami-01ca192a9fcff72f3 Launch in EC2
ap-southeast-1 ami-08429cbf9ddea6ecb Launch in EC2
ap-southeast-2 ami-066df086af805c66b Launch in EC2
ca-central-1 ami-013fa8fef42db8b36 Launch in EC2
eu-central-1 ami-030e83db2544120e9 Launch in EC2
eu-west-1 ami-06e668fb1b137630d Launch in EC2
eu-west-2 ami-0d0bfe2c76229589e Launch in EC2
sa-east-1 ami-0f8a7b9fadcb3e816 Launch in EC2
us-east-1 ami-010d756a934c43927 Launch in EC2
us-east-2 ami-044b55fc730280ba3 Launch in EC2
us-west-1 ami-0ed2d8e33eabd0294 Launch in EC2
us-west-2 ami-053bfbb7aeedb7613 Launch in EC2

arm64 hvm gp2 AMIs

Region AMI ID Direct launch link
ap-northeast-1 ami-00a4c5cfc162ae5d2 Launch in EC2
ap-northeast-2 ami-00a7b51981839b167 Launch in EC2
ap-south-1 ami-09c196a2acb1e2ef2 Launch in EC2
ap-southeast-1 ami-0ca9b2016f6efaf75 Launch in EC2
ap-southeast-2 ami-0e3f06954d78db89f Launch in EC2
ca-central-1 ami-018c47e185cc01f9e Launch in EC2
eu-central-1 ami-0ed9396544d2b32fb Launch in EC2
eu-west-1 ami-00514a89341887b63 Launch in EC2
eu-west-2 ami-0e9f1a852f138fce4 Launch in EC2
sa-east-1 ami-0f584851335cc9b56 Launch in EC2
us-east-1 ami-03e60a119bba14c43 Launch in EC2
us-east-2 ami-06d43955eb2b078fe Launch in EC2
us-west-1 ami-04adbd3a0e47df370 Launch in EC2
us-west-2 ami-0ae39d05602b807cb 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.3 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
Pass pass dustymabe
Pass pass nielsenb
Pass pass cyberpear
Basic QA:Testcase_base_system_logging
Bot Pass pass coconut
Pass pass dustymabe
Pass pass nielsenb
Pass pass cyberpear
Final QA:Testcase_base_services_start
Bot Pass pass coconut
Pass pass dustymabe
Pass pass nielsenb
Warning warn cyberpear
[1]
Final QA:Testcase_base_selinux
Bot Pass pass coconut
Pass pass dustymabe
Pass pass nielsenb
Pass pass cyberpear
Final QA:Testcase_base_service_manipulation
Bot Pass pass coconut
Pass pass dustymabe
Pass pass nielsenb
Warning warn cyberpear
[2]
  1. Apr 15 23:09:45 f32-rc1.3 dbus-broker-launch[602]: Activation request for 'org.freedesktop.resolve1' failed: The systemd unit 'dbus-org.freedesktop.resolve1.service' could not be found.
  2. 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