Test Results:Fedora 34 Rawhide 20210206.n.0 Cloud

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

Which tests to run

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
Xfce live				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
Scientific vagrant-libvirt				Download
Scientific vagrant-virtualbox				Download
Comp_Neuro live				Download
Games live				Download
Python_Classroom live				Download
Robotics live				Download
Workstation raw-xz	Download
Server raw-xz	Download
KDE raw-xz	Download
Minimal raw-xz	Download
SoaS raw-xz		Download
LXDE raw-xz		Download
Python_Classroom raw-xz		Download
Server_Appliance raw-xz		Download
Silverblue dvd-ostree	Download
KDE_Appliance raw-xz		Download
LXQt raw-xz		Download
Minimal_Appliance raw-xz		Download
Xfce_Appliance raw-xz		Download
Workstation_Appliance raw-xz		Download

x86_64 hvm standard AMIs

Region	AMI ID	Direct launch link
ap-northeast-1	ami-0ab3fabf03fab567f	Launch in EC2
ap-northeast-2	ami-063ac6b483ac00c6e	Launch in EC2
ap-south-1	ami-0f35f66558b58ab14	Launch in EC2
ap-southeast-1	ami-01d548fa0e4b189ee	Launch in EC2
ap-southeast-2	ami-038c369810a847991	Launch in EC2
ca-central-1	ami-0906281e115307cc8	Launch in EC2
eu-central-1	ami-074da1e6dee928311	Launch in EC2
eu-west-1	ami-0292bb3a573918736	Launch in EC2
eu-west-2	ami-065104e55e9e9f96a	Launch in EC2
sa-east-1	ami-098d3e3fcda756d4c	Launch in EC2
us-east-1	ami-0dde5a1d471c55f3a	Launch in EC2
us-east-2	ami-04e5c3f80ffa450af	Launch in EC2
us-west-1	ami-08b638af3dfe93589	Launch in EC2
us-west-2	ami-034df00f5ad663f88	Launch in EC2

x86_64 hvm gp2 AMIs

Region	AMI ID	Direct launch link
ap-northeast-1	ami-09947a7a7e3ea4620	Launch in EC2
ap-northeast-2	ami-0c2f34a7b63f725ba	Launch in EC2
ap-south-1	ami-0171b4aff4db84011	Launch in EC2
ap-southeast-1	ami-065a119227fdc5117	Launch in EC2
ap-southeast-2	ami-0e991b9f43bdca781	Launch in EC2
ca-central-1	ami-0bdf5f5addffa0ad1	Launch in EC2
eu-central-1	ami-0510cfd36ff86dea0	Launch in EC2
eu-west-1	ami-062b1f2a694752073	Launch in EC2
eu-west-2	ami-00c48d894b7129eb4	Launch in EC2
sa-east-1	ami-0fcd1eb1a22c0454a	Launch in EC2
us-east-1	ami-00b846f7d4fee747a	Launch in EC2
us-east-2	ami-010a179373f99a48c	Launch in EC2
us-west-1	ami-09891298d4b78276b	Launch in EC2
us-west-2	ami-0d463b3313b64c167	Launch in EC2

arm64 hvm standard AMIs

Region	AMI ID	Direct launch link
ap-northeast-1	ami-0b0407472011a88d9	Launch in EC2
ap-northeast-2	ami-0af22a2e62191e795	Launch in EC2
ap-south-1	ami-0619553b2205b93b4	Launch in EC2
ap-southeast-1	ami-09e6d46629d2099db	Launch in EC2
ap-southeast-2	ami-0467af6c52a6de9bc	Launch in EC2
ca-central-1	ami-0bda5c7fe46f4b8e5	Launch in EC2
eu-central-1	ami-03c6618d960c58571	Launch in EC2
eu-west-1	ami-06955e47f7fd3232f	Launch in EC2
eu-west-2	ami-026c7f6d9be4aa84d	Launch in EC2
sa-east-1	ami-007b602442cfa2763	Launch in EC2
us-east-1	ami-0f35f217a0ce07cd3	Launch in EC2
us-east-2	ami-0432c7f6df26388a8	Launch in EC2
us-west-1	ami-0ba22fc364244c957	Launch in EC2
us-west-2	ami-05b058918386d94cd	Launch in EC2

arm64 hvm gp2 AMIs

Region	AMI ID	Direct launch link
ap-northeast-1	ami-0238207851a6ac369	Launch in EC2
ap-northeast-2	ami-0a4930c3b04c501dc	Launch in EC2
ap-south-1	ami-052d53ee2646ff514	Launch in EC2
ap-southeast-1	ami-0a0cfc10723ae370b	Launch in EC2
ap-southeast-2	ami-043f170abb0245226	Launch in EC2
ca-central-1	ami-05427577614ae903b	Launch in EC2
eu-central-1	ami-0556a99c00d58f814	Launch in EC2
eu-west-1	ami-095d7d61c5862c6d2	Launch in EC2
eu-west-2	ami-0f01c34365d1a0cb2	Launch in EC2
sa-east-1	ami-0627bdd43a7216801	Launch in EC2
us-east-1	ami-06aac226eb99fe2ae	Launch in EC2
us-east-2	ami-013efc536056d4ca3	Launch in EC2
us-west-1	ami-05cd8d2f712177da5	Launch in EC2
us-west-2	ami-0494683dc4a8e8b6b	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

The Test Results:Fedora 34 Rawhide 20210206.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 robatino	Passed - The test has been run and the tester determine the test met the expected results	{{result|pass|robatino}}
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 jlaska	Failed - Indicates a failed test. A link to a bug must be provided. See Template:Result for details on providing bug information.	{{result|fail|jlaska|XYZ|ZXY}}
warn rhe	Warning - This test completed and met the expected results of the test, but other issues were encountered during testing that warrant attention.	{{result|warn|rhe}} <ref>Brief description about the warning status</ref>
pass hongqing warn kparal	Multiple results - More people can easily provide results to a single test case.	{{result|pass|hongqing}} {{result|warn|kparal}}
fail pboy	Failed - Same issue with LVM again	{{result|fail|pboy|2246871|2244305}}
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	pass coconut	none	none	none
Basic	QA:Testcase_base_system_logging	pass coconut	none	none	none
Basic	QA:Testcase_base_update_cli	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	pass coconut	none	none	none
Final	QA:Testcase_base_selinux	pass coconut	none	none	none
Final	QA:Testcase_base_service_manipulation	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	pass coconut	none	none
Basic	QA:Testcase_base_system_logging	pass coconut	none	none
Basic	QA:Testcase_base_update_cli	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	pass coconut	none	none
Final	QA:Testcase_base_selinux	pass coconut	none	none
Final	QA:Testcase_base_service_manipulation	pass coconut	none	none