Architectures/PowerPC/Fedora 32 PowerPC Cloud: Difference between revisions

Revision as of 15:03, 2 April 2020

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 20200401.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
Workstation live			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 vmdk	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
Container_Minimal_Base docker	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		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-0f4718436685a79aa	Launch in EC2
ap-northeast-2	ami-07c77edf7a83b9580	Launch in EC2
ap-south-1	ami-09b018d15fef89dc4	Launch in EC2
ap-southeast-1	ami-0d8b8fb81d8f1f95f	Launch in EC2
ap-southeast-2	ami-0f0ec22f258e50fef	Launch in EC2
ca-central-1	ami-0be3a5708661b952c	Launch in EC2
eu-central-1	ami-01a81896060e40504	Launch in EC2
eu-west-1	ami-04b0ff17b2b9bc117	Launch in EC2
eu-west-2	ami-06cba7abdd25ec54b	Launch in EC2
sa-east-1	ami-0ef5cd1ee553202e4	Launch in EC2
us-east-1	ami-08e752e6a52d9c35c	Launch in EC2
us-east-2	ami-0547d6fcf74a9895e	Launch in EC2
us-west-1	ami-02d545d613a18ef34	Launch in EC2
us-west-2	ami-06cc4ac0d54b62138	Launch in EC2

x86_64 hvm gp2 AMIs

Region	AMI ID	Direct launch link
ap-northeast-2	ami-0bdf2cef00cdcad28	Launch in EC2
ap-south-1	ami-03b38c776c27446bf	Launch in EC2
ap-southeast-1	ami-004412d72f3fc9313	Launch in EC2
ap-southeast-2	ami-0a368756d425e3b36	Launch in EC2
ca-central-1	ami-0b859e13fa40f70b1	Launch in EC2
eu-west-1	ami-0035db59e78d2f0bd	Launch in EC2
sa-east-1	ami-01ad4e772a49ef6e7	Launch in EC2
us-east-1	ami-01cb62126e3541e51	Launch in EC2
us-east-2	ami-0ebca43f030aba585	Launch in EC2

arm64 hvm standard AMIs

Region	AMI ID	Direct launch link
us-east-1	ami-068bc74b958b846d2	Launch in EC2

arm64 hvm gp2 AMIs

Region	AMI ID	Direct launch link
us-east-1	ami-0ca7dcab2fa915d43	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 32 Branched 20200401.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

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).
Once reviewed, make your changes to any current documents that use the template (e.g. Test_Results:Current_Cloud_Test).
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 ^[1] ^[2]	Failed - Indicates a failed test. A link to a bug must be provided. See Template:Result for details on providing bug information. ↑ RHBZ #XYZ ↑ RHBZ #ZXY	`{{result\|fail\|jlaska\|XYZ\|ZXY}}`
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. ↑ Brief description about the warning status	`{{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 ^[1] ^[2]	Failed - Same issue with LVM again ↑ RHBZ #2246871 ↑ RHBZ #'2244305	`{{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

Get an AWS account (the approval process can take hours)
Make sure that your security group allows for SSH (default tcp port 22)
Log in to the AWS Management Console
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
Search for and select the desired AMI on the IMAGES/AMIs section of the EC2 console
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

Use your own OpenStack deployment
Provide or create an SSH keypair
Make sure that your security group allows for SSH (default tcp port 22)
Log in to the Horizon dashboard
Find the image URL at http://cloud.fedoraproject.org/ or as provided in release candidate documents.
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
Launch the instance (in the dashboard, under the "Images" heading, click the "Launch" button for the appropriate image

Local testing

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.
Once logged in the virtual cloud instance, you can perform the tests below.

Cloud base (qcow2) Local tests

Milestone	Test Case	Bare Metal		PKVM		PVM LPAR
Milestone	Test Case	P8	P9	P8	P9	P8	P9
Basic	QA:Testcase_base_startup	none	none	pass f32-20200401.n.1 openqa	none	none	none
Basic	QA:Testcase_base_system_logging	none	none	pass f32-20200401.n.1 openqa	none	none	none
Basic	QA:Testcase_base_update_cli	none	none	pass f32-20200401.n.1 openqa	none	none	none
Final	QA:Testcase_Services_start	none	none	pass f32-20200401.n.1 openqa	none	none	none
Final	QA:Testcase_base_selinux	none	none	pass f32-20200401.n.1 openqa	none	none	none
Final	QA:Testcase_base_service_manipulation	none	none	pass f32-20200401.n.1 openqa	none	none	none

Cloud base (raw-xz) Local tests

Milestone	Test Case	Bare Metal		PKVM		PVM LPAR
Milestone	Test Case	P8	P9	P8	P9	P8	P9
Basic	QA:Testcase_base_startup	none	none	pass f32-20200401.n.1 openqa	none	none	none
Basic	QA:Testcase_base_update_cli	none	none	pass f32-20200401.n.1 openqa	none	none	none

Container Base (tar.xz) Local tests

Run container
This test load the image, check the image is loaded, run the container, check the container is running, send commands to the container, stop the container, check the container is stopped.

Milestone	Test Case	Bare Metal		PKVM		PVM LPAR
Milestone	Test Case	P8	P9	P8	P9	P8	P9
Optional	QA:Testcase_base_startup Podman	none	none	pass f32-20200401.n.1 openqa	none	none	none
Optional	QA:Testcase_base_startup Docker	none	none	pass f32-20200401.n.1 openqa	none	none	none

Container Minimal Base (tar.xz) Local tests