Test Results:Fedora 34 Beta 1.3 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 Beta 1.3 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
Container_Base docker	Download	Download	Download	Download	Download
Container_Minimal_Base docker	Download	Download	Download	Download	Download
Python_Classroom vagrant-libvirt					Download
Python_Classroom vagrant-virtualbox					Download
Scientific vagrant-libvirt					Download
Scientific 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
Robotics live					Download
Scientific_KDE 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
KDE raw-xz	Download	Download
Minimal raw-xz	Download	Download
Xfce raw-xz	Download	Download
SoaS raw-xz	Download	Download
Python_Classroom raw-xz		Download

x86_64 hvm standard AMIs

Region	AMI ID	Direct launch link
ap-northeast-1	ami-01e43469636726a68	Launch in EC2
ap-northeast-2	ami-0b56b82086fb70159	Launch in EC2
ap-south-1	ami-03d61c6ee6cb5788e	Launch in EC2
ap-southeast-1	ami-03898bc7215633ff4	Launch in EC2
ap-southeast-2	ami-03068d250ed7261ca	Launch in EC2
ca-central-1	ami-0fc34fc28f5e75f09	Launch in EC2
eu-central-1	ami-0adb38d61805fc555	Launch in EC2
eu-west-1	ami-0f916556fdd8764ca	Launch in EC2
eu-west-2	ami-020a2735fffcae531	Launch in EC2
sa-east-1	ami-0b6d70411f12a679f	Launch in EC2
us-east-1	ami-011696656634da9b6	Launch in EC2
us-east-2	ami-027ffc520db91584b	Launch in EC2
us-west-1	ami-099fb60786cdfef7a	Launch in EC2
us-west-2	ami-0327dcfb6f596478f	Launch in EC2

x86_64 hvm gp2 AMIs

Region	AMI ID	Direct launch link
ap-northeast-1	ami-00136e5db1273ec43	Launch in EC2
ap-northeast-2	ami-00c469b9c36fd620a	Launch in EC2
ap-south-1	ami-08733b21b3a10dc26	Launch in EC2
ap-southeast-1	ami-0bcec9ac02bbd228c	Launch in EC2
ap-southeast-2	ami-0338eb6622cc6a75f	Launch in EC2
ca-central-1	ami-04a5b27c9e0ad978a	Launch in EC2
eu-central-1	ami-04f4a1621f5249776	Launch in EC2
eu-west-1	ami-0df0866557b263a88	Launch in EC2
eu-west-2	ami-03e07863f210191d1	Launch in EC2
sa-east-1	ami-0437f8b596968c295	Launch in EC2
us-east-1	ami-00da07c8f705da39b	Launch in EC2
us-east-2	ami-0784e9a05eb9f7ab1	Launch in EC2
us-west-1	ami-0f384da2d97dbdd1a	Launch in EC2
us-west-2	ami-0d5f0cad3a83f7ccc	Launch in EC2

arm64 hvm standard AMIs

Region	AMI ID	Direct launch link
ap-northeast-1	ami-062b8fbb573e0d340	Launch in EC2
ap-northeast-2	ami-028d34e8612f0acee	Launch in EC2
ap-south-1	ami-00c88165772d1b4f8	Launch in EC2
ap-southeast-1	ami-0e474cd482ec1e776	Launch in EC2
ap-southeast-2	ami-05bc00e9965a2aa6b	Launch in EC2
ca-central-1	ami-08aba773b948a737d	Launch in EC2
eu-central-1	ami-0568ce9253e59f531	Launch in EC2
eu-west-1	ami-0a8f6a75e78717ccf	Launch in EC2
eu-west-2	ami-0c31ef6de97b4638c	Launch in EC2
sa-east-1	ami-09794b22fc57e863e	Launch in EC2
us-east-1	ami-0804783e2772e523b	Launch in EC2
us-east-2	ami-0cb03112561729282	Launch in EC2
us-west-1	ami-0f57010a52bce697b	Launch in EC2
us-west-2	ami-0665b8c4cbb368bab	Launch in EC2

arm64 hvm gp2 AMIs

Region	AMI ID	Direct launch link
ap-northeast-1	ami-069c6b8fc7c675cc9	Launch in EC2
ap-northeast-2	ami-0a7b280453eec1525	Launch in EC2
ap-south-1	ami-0f1822558f076bc59	Launch in EC2
ap-southeast-1	ami-09b329eaa4943fd6a	Launch in EC2
ap-southeast-2	ami-0db0cf559df42fadb	Launch in EC2
ca-central-1	ami-0f416f52473ae884f	Launch in EC2
eu-central-1	ami-0e1d29a42300a50fd	Launch in EC2
eu-west-1	ami-01454e985b27f61c6	Launch in EC2
eu-west-2	ami-0aaba6c6ec9c3c853	Launch in EC2
sa-east-1	ami-0c23f66932aa2e928	Launch in EC2
us-east-1	ami-024947169ddaaf965	Launch in EC2
us-east-2	ami-0271abc45ea744b0b	Launch in EC2
us-west-1	ami-023261004f55a6937	Launch in EC2
us-west-2	ami-066fe560d5247fa00	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 Beta 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 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	pass coremodule	none	none
Basic	QA:Testcase_base_reboot_unmount	pass coconut	pass coremodule	none	none
Basic	QA:Testcase_base_system_logging	pass coconut	pass coremodule	none	none
Basic	QA:Testcase_base_update_cli	pass coconut	pass coremodule	none	none
Basic / Beta	QA:Testcase_package_install_remove	none	pass coremodule	none	none
Basic / Final	QA:Testcase_base_artwork_release_identification	none	pass coremodule	none	none
Final	QA:Testcase_base_edition_self_identification	none	pass coremodule	none	none
Final	QA:Testcase_base_services_start	pass coconut	pass coremodule	none	none
Final	QA:Testcase_base_selinux	pass coconut	pass coremodule	none	none
Final	QA:Testcase_base_service_manipulation	pass coconut	pass coremodule	none	none

aarch64

Milestone	Test Case	Local	EC2 (KVM)	Openstack
Basic	QA:Testcase_base_startup	pass coconut	pass previous 1.2 run	none
Basic	QA:Testcase_base_reboot_unmount	pass coconut	pass previous 1.2 run	none
Basic	QA:Testcase_base_system_logging	pass coconut	pass previous 1.2 run	none
Basic	QA:Testcase_base_update_cli	pass coconut	pass previous 1.2 run	none
Basic / Beta	QA:Testcase_package_install_remove	none	pass previous 1.2 run	none
Basic / Final	QA:Testcase_base_artwork_release_identification	none	pass previous 1.2 run	none
Final	QA:Testcase_base_edition_self_identification	none	pass previous 1.2 run	none
Final	QA:Testcase_base_services_start	pass coconut	pass previous 1.2 run	none
Final	QA:Testcase_base_selinux	pass coconut	pass previous 1.2 run	none
Final	QA:Testcase_base_service_manipulation	pass coconut	none	none