Test Results:Fedora 35 Rawhide 20210526.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 35 20210526.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	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
SoaS live					Download
Mate live					Download
Cinnamon live					Download
LXDE live					Download
Container_Minimal_Base docker				Download	Download
Kinoite dvd-ostree	Download		Download		Download
Python_Classroom vagrant-libvirt					Download
Python_Classroom vagrant-virtualbox					Download
Design_suite live					Download
Python_Classroom 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
Minimal raw-xz	Download	Download
Xfce raw-xz	Download	Download
Container_Base docker				Download

x86_64 hvm standard AMIs

Region	AMI ID	Direct launch link
ap-northeast-1	ami-0fb614e1b73521fb7	Launch in EC2
ap-northeast-2	ami-09bf5681a9beb61a9	Launch in EC2
ap-south-1	ami-0d626fa2c8642960f	Launch in EC2
ap-southeast-1	ami-0c84511101f7a06bb	Launch in EC2
ap-southeast-2	ami-0cde12365310efa72	Launch in EC2
ca-central-1	ami-01510614886b645b8	Launch in EC2
eu-central-1	ami-0ab7880f66729206a	Launch in EC2
eu-west-1	ami-05de259457538f436	Launch in EC2
eu-west-2	ami-0f01df70edea5efba	Launch in EC2
sa-east-1	ami-085f172f540949857	Launch in EC2
us-east-1	ami-06a4cd234eb5ecb1a	Launch in EC2
us-east-2	ami-0deff5fab857589d6	Launch in EC2
us-west-1	ami-028d813964ed599e3	Launch in EC2
us-west-2	ami-012088d2f3f53be03	Launch in EC2

x86_64 hvm gp2 AMIs

Region	AMI ID	Direct launch link
ap-northeast-1	ami-0f2b7eb99979cdba2	Launch in EC2
ap-northeast-2	ami-09efd2b15ac4a5711	Launch in EC2
ap-south-1	ami-0ce85bf7f23e97686	Launch in EC2
ap-southeast-1	ami-0396df8ba9d6acd03	Launch in EC2
ap-southeast-2	ami-07599c9fe5af71ef2	Launch in EC2
ca-central-1	ami-08a5f4d3ba9252002	Launch in EC2
eu-central-1	ami-0f0898f0578ff8db6	Launch in EC2
eu-west-1	ami-0b144da67cd26e816	Launch in EC2
eu-west-2	ami-0817718e1e142a0ee	Launch in EC2
sa-east-1	ami-0c1059eb1ddf7a027	Launch in EC2
us-east-1	ami-0774eacc7d0e4cb82	Launch in EC2
us-east-2	ami-0bb279663430c30d3	Launch in EC2
us-west-1	ami-00c2878d19814c303	Launch in EC2
us-west-2	ami-0c404a0d8c33ba248	Launch in EC2

arm64 hvm standard AMIs

Region	AMI ID	Direct launch link
ap-northeast-1	ami-0b3219d20925cdb3b	Launch in EC2
ap-northeast-2	ami-04ffd1f5db919be47	Launch in EC2
ap-south-1	ami-08f78c7c211e56d76	Launch in EC2
ap-southeast-1	ami-028c9abc45be11931	Launch in EC2
ap-southeast-2	ami-071908696932143d8	Launch in EC2
ca-central-1	ami-0ad53e4dc03c8be59	Launch in EC2
eu-central-1	ami-023a82b4811988531	Launch in EC2
eu-west-1	ami-02731d94ebf284f2d	Launch in EC2
eu-west-2	ami-080069aea4224bf58	Launch in EC2
sa-east-1	ami-0c8ac4a0e1f61e3bf	Launch in EC2
us-east-1	ami-0a95e1aaa42b1b7e1	Launch in EC2
us-east-2	ami-04e679b49e265308a	Launch in EC2
us-west-1	ami-0f5fe36be592f742b	Launch in EC2
us-west-2	ami-0390775bb2e1e514d	Launch in EC2

arm64 hvm gp2 AMIs

Region	AMI ID	Direct launch link
ap-northeast-1	ami-06081a21597f9d31f	Launch in EC2
ap-northeast-2	ami-0fc7b5827d1088f14	Launch in EC2
ap-south-1	ami-0033dd5c6ff1a0ca4	Launch in EC2
ap-southeast-1	ami-0b955b7a1cee4b7d7	Launch in EC2
ap-southeast-2	ami-08009726cbc452fcf	Launch in EC2
ca-central-1	ami-09d3e8b7bfda39516	Launch in EC2
eu-central-1	ami-04f5bade60ab76ee6	Launch in EC2
eu-west-1	ami-0a1bca6acf18f3cd5	Launch in EC2
eu-west-2	ami-0a540df0186a2590b	Launch in EC2
sa-east-1	ami-0e0875e971ee59a30	Launch in EC2
us-east-1	ami-0059081d974085b45	Launch in EC2
us-east-2	ami-029fea9ceaf24fb1d	Launch in EC2
us-west-1	ami-08594ddb161e56317	Launch in EC2
us-west-2	ami-05119e75555344f89	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 20210526.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	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	pass coconut	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	pass coconut	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	pass coconut	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