Test Results:Fedora 35 Rawhide 20210428.n.1 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 35 20210428.n.1 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	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	Download
Cloud_Base raw-xz	Download		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
SoaS live					Download
Mate live					Download
Cinnamon live					Download
LXDE live					Download
Design_suite live					Download
Jam_KDE live					Download
Silverblue dvd-ostree	Download		Download		Download
LXQt live					Download
i3 live					Download
Workstation raw-xz	Download	Download
Server raw-xz	Download	Download
Minimal raw-xz	Download	Download
Xfce raw-xz	Download	Download

x86_64 hvm standard AMIs

Region	AMI ID	Direct launch link
ap-northeast-1	ami-05cc80762be8419dc	Launch in EC2
ap-northeast-2	ami-0d7dbd2b8f0053750	Launch in EC2
ap-south-1	ami-02b9b60ece2e84e44	Launch in EC2
ap-southeast-1	ami-0f11f23634c7627ab	Launch in EC2
ap-southeast-2	ami-05b18b7ebd44d2762	Launch in EC2
ca-central-1	ami-0722f9eb177f8e0f3	Launch in EC2
eu-central-1	ami-0caeba0a1322b5ca8	Launch in EC2
eu-west-1	ami-0cddc288e73b92b00	Launch in EC2
eu-west-2	ami-0d516d52071b37572	Launch in EC2
sa-east-1	ami-0de599e22cdcc5fb6	Launch in EC2
us-east-1	ami-00de5be48709f82a5	Launch in EC2
us-east-2	ami-0e6b4da858903e0dc	Launch in EC2
us-west-1	ami-012c2274935c2a57e	Launch in EC2
us-west-2	ami-04384946ddf1757fa	Launch in EC2

x86_64 hvm gp2 AMIs

Region	AMI ID	Direct launch link
ap-northeast-1	ami-03a47a2dd22f9b06e	Launch in EC2
ap-northeast-2	ami-0364353ab99511e62	Launch in EC2
ap-south-1	ami-0cfba1c95aea79fa9	Launch in EC2
ap-southeast-1	ami-02861b40b943121d2	Launch in EC2
ap-southeast-2	ami-0a1ee9b59016e50cc	Launch in EC2
ca-central-1	ami-0bf3a501395495dc5	Launch in EC2
eu-central-1	ami-0124a4b8898dc0251	Launch in EC2
eu-west-1	ami-08744f71928beaaeb	Launch in EC2
eu-west-2	ami-0a17af028a3d41efe	Launch in EC2
sa-east-1	ami-045b1227c31f39fe4	Launch in EC2
us-east-1	ami-0d9810ffb21abd35c	Launch in EC2
us-east-2	ami-06e8a58abbc4b9af7	Launch in EC2
us-west-1	ami-0b871d8ed48fe2bb7	Launch in EC2
us-west-2	ami-07b324044c9e5d479	Launch in EC2

arm64 hvm standard AMIs

Region	AMI ID	Direct launch link
ap-northeast-1	ami-07618a6211d22eb37	Launch in EC2
ap-northeast-2	ami-00b33c3549b343641	Launch in EC2
ap-south-1	ami-0ca31336fdeb307a0	Launch in EC2
ap-southeast-1	ami-02db5c54ec5692d76	Launch in EC2
ap-southeast-2	ami-05a5fa83ec10b7d9b	Launch in EC2
ca-central-1	ami-0a9a815e0295cf3ff	Launch in EC2
eu-central-1	ami-06e694fe092b42883	Launch in EC2
eu-west-1	ami-0824d8e122d51498c	Launch in EC2
eu-west-2	ami-0b960177a7b8e042b	Launch in EC2
sa-east-1	ami-0cd2ef0be35eef17c	Launch in EC2
us-east-1	ami-0dbb2e385ced039a9	Launch in EC2
us-east-2	ami-0577e95403588a3e7	Launch in EC2
us-west-1	ami-00781801295c10d27	Launch in EC2
us-west-2	ami-0d17d8d1c40a80f8a	Launch in EC2

arm64 hvm gp2 AMIs

Region	AMI ID	Direct launch link
ap-northeast-1	ami-059bbea532b7dc04c	Launch in EC2
ap-northeast-2	ami-00c8ae6c2e2392739	Launch in EC2
ap-south-1	ami-08b720e794647177a	Launch in EC2
ap-southeast-1	ami-0b40681e9f69f0b81	Launch in EC2
ap-southeast-2	ami-0efebdf64e30efae8	Launch in EC2
ca-central-1	ami-092ecb4783ea9ab21	Launch in EC2
eu-central-1	ami-06004bd21182c9740	Launch in EC2
eu-west-1	ami-0626fea8a3c01ddd2	Launch in EC2
eu-west-2	ami-064f684fb4238a978	Launch in EC2
sa-east-1	ami-04f64bdceec5babcd	Launch in EC2
us-east-1	ami-030ed5c763ff1aa6d	Launch in EC2
us-east-2	ami-0f0d99dbde08bbf1e	Launch in EC2
us-west-1	ami-003f11d329399919a	Launch in EC2
us-west-2	ami-0ed3b5680089a30c3	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 35 Rawhide 20210428.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

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	pass coconut	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