From Fedora Project Wiki

This page records Cloud validation testing test results for the Fedora 45 20260505.n.0 nightly compose.

Which tests to run[edit]

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[edit]

1. Download one or more media for testing, or for EC2 tests, locate and use an appropriate AMI:

Image aarch64 ppc64le s390x x86_64
Everything boot Download Download Download Download
Workstation live Download Download
Server dvd Download Download Download Download
Server boot Download Download Download Download
Cloud_Base raw-xz Download Download
Cloud_Base vhd-compressed Download Download
Cloud_Base tar-gz Download Download
Cloud_Base qcow2 Download Download Download Download
Cloud_Base vagrant-libvirt Download Download
Cloud_Base vagrant-virtualbox Download
KDE live Download Download Download
Xfce live Download Download
SoaS live Download Download
Mate live Download
Cinnamon live Download
LXDE live Download
Budgie-Atomic dvd-ostree Download
COSMIC-Atomic bootable-container Download Download
COSMIC-Atomic dvd-ostree Download Download
Cloud_Base_UKI qcow2 Download Download
Container_Minimal_Base container Download Download Download Download
Container_Base container Download Download Download Download
Container_Toolbox container Download Download Download Download
WSL_Base wsl2 Download Download
FEX_RootFS fex Download
Kinoite qcow2 Download Download
Kinoite bootable-container Download Download
Kinoite dvd-ostree Download Download
Python_Classroom vagrant-libvirt Download Download
Scientific vagrant-libvirt Download Download
Python_Classroom live Download Download
Scientific_KDE live Download Download
Python_Classroom vagrant-virtualbox Download
Scientific vagrant-virtualbox Download
Astronomy_KDE live Download
Design_suite live Download
Games live Download
Jam_KDE live Download
Robotics live Download
Security live Download
Server_KVM qcow2 Download Download Download
Silverblue qcow2 Download Download
Silverblue bootable-container Download Download
Silverblue dvd-ostree-osbuild Download Download
Silverblue dvd-ostree Download Download
COSMIC live Download Download
KDE_Mobile live Download Download
LXQt live Download Download
i3 live Download Download
Budgie live Download
Sway live Download
Sway-Atomic dvd-ostree Download
Workstation raw-xz Download
Server raw-xz Download
KDE raw-xz Download
Minimal raw-xz Download
Xfce raw-xz Download
SoaS raw-xz Download
Kinoite raw-xz Download
Python_Classroom raw-xz Download
Scientific_KDE raw-xz Download
Silverblue raw-xz Download
COSMIC raw-xz Download
KDE_Mobile raw-xz Download
LXQt raw-xz Download

x86_64 AMIs[edit]

Region AMI ID Direct launch link
us-east-1 ami-0f7ea44daf4a5d0cc Launch in EC2
af-south-1 ami-0f7f376e8be920c8c Launch in EC2
eu-north-1 ami-0f1086bef0efbf18e Launch in EC2
ap-south-1 ami-009048eb7a6fd7cd3 Launch in EC2
eu-west-3 ami-003cd745f3c7bbe2f Launch in EC2
eu-west-2 ami-03b4a1f24b0624ae0 Launch in EC2
eu-south-1 ami-0f071226128f08760 Launch in EC2
eu-west-1 ami-0edbfe4ee699576ed Launch in EC2
ap-northeast-3 ami-00a405317cd2a942d Launch in EC2
ap-northeast-2 ami-07f5b2c6f70ccdc9a Launch in EC2
ap-northeast-1 ami-061b6994dd1324c24 Launch in EC2
sa-east-1 ami-0358a1cc3acaffb2f Launch in EC2
ca-central-1 ami-055cff39a75a306d6 Launch in EC2
ap-east-1 ami-082dd501c044f97a4 Launch in EC2
ap-southeast-1 ami-0f98afe0699ddfab4 Launch in EC2
ap-southeast-2 ami-02d23510584242059 Launch in EC2
ap-southeast-3 ami-0f5387786f9252dd8 Launch in EC2
eu-central-1 ami-094f0d9ae8ec03d13 Launch in EC2
us-east-2 ami-01a7bbe4b87ff5110 Launch in EC2
us-west-1 ami-0e7bf6b2247eaee1a Launch in EC2
us-west-2 ami-080f0076e3d5face8 Launch in EC2

aarch64 AMIs[edit]

Region AMI ID Direct launch link
us-east-1 ami-064e680d308023586 Launch in EC2
af-south-1 ami-052bd870ebb3da19f Launch in EC2
eu-north-1 ami-08172a9ce05559494 Launch in EC2
ap-south-1 ami-000e41b4936caba1a Launch in EC2
eu-west-3 ami-0b14d774a4240af21 Launch in EC2
eu-west-2 ami-0f9dc97aa5414de94 Launch in EC2
eu-south-1 ami-0d94135492beb587a Launch in EC2
eu-west-1 ami-0f60f50d6432c8358 Launch in EC2
ap-northeast-3 ami-026a3534e3a52d28b Launch in EC2
ap-northeast-2 ami-08ec9e91aebb854ed Launch in EC2
ap-northeast-1 ami-088fd0331e23ec135 Launch in EC2
sa-east-1 ami-05c5d2487018a1eba Launch in EC2
ca-central-1 ami-0f09194a1d1e5e7bd Launch in EC2
ap-east-1 ami-0627b26d922462535 Launch in EC2
ap-southeast-1 ami-0d2c62a3cb20dc63a Launch in EC2
ap-southeast-2 ami-04959cbc679ad0047 Launch in EC2
ap-southeast-3 ami-034f3cacbe4a029b2 Launch in EC2
eu-central-1 ami-0eb677b37557c3b21 Launch in EC2
us-east-2 ami-037f88d9b0a7fe7a5 Launch in EC2
us-west-1 ami-0994c4f3ad94c7945 Launch in EC2
us-west-2 ami-0a7e01986d912444d 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[edit]

The Test Results:Fedora 45 Rawhide 20260505.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[edit]

  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[edit]

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 pass robatino
Passed - The test has been run and the tester determine the test met the expected results {{result|pass|robatino}}
Inprogress 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 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.
  1. ↑ RHBZ #XYZ
  2. ↑ RHBZ #ZXY
{{result|fail|jlaska|XYZ|ZXY}}
Warning 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.
  1. ↑ Brief description about the warning status
{{result|warn|rhe}} <ref>Brief description about the warning status</ref>
Pass pass hongqing
Warning warn kparal
Multiple results - More people can easily provide results to a single test case. {{result|pass|hongqing}} {{result|warn|kparal}}
Fail fail pboy [1] [2]
Failed - Same issue with LVM again
  1. ↑ RHBZ #2246871
  2. ↑ RHBZ #'2244305
{{result|fail|pboy|2246871|2244305}}
Pass 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[edit]

Cloud Provider Setup[edit]

Expand one of the sections below for instructions on setting up and running these testcases on a specific provider. More information can be found on the Fedora Cloud page and the Cloud Working Group website.

Amazon EC2 (via management console)[edit]

Personal account[edit]
  1. Obtain an AWS account (the approval process can take several hours).
Fedora group account[edit]

Amazon provides us with a community account. This account is currently used by: Fedora Infra, CentOS, Fedora-CI, openQA, logdetective, CoreOS, Cloud, ABRT, and others.

To avoid costs, you can contact the Infrastructure team and request access to Fedora's AWS account for testing purposes, per this SOP.

  1. Check your groups at https://accounts.fedoraproject.org/user/<ACCOUNT>.
  2. You must be in the aws-* FAS group (or another group with access) to perform this action.
  3. To access the AWS Console via Ipsilon authentication, use this SAML link.

Launch an Instance[edit]

  1. Log in to the AWS Management Console.
  2. Navigate to the EC2 console.
  3. To select the desired Amazon Machine Image (AMI), you can either:
    • Use the "Direct launch link" (if provided).
    • Search for and select the desired AMI in the IMAGES > AMIs section of the EC2 console.
  4. Ensure that your instance's security group is configured to allow SSH access (default TCP port 22).
  5. Launch an instance with the AMI.

Amazon EC2 (via Testing Farm)[edit]

Testing Farm Access - Testing Farm provides a streamlined way for Fedora and CentOS Stream contributors to access Amazon machines for testing. More information about public ranch users can be found here.

  1. Access Method: You can access Amazon images via Testing Farm; see the installation steps.
  2. Obtain API Key: Generate your public API key for Testing Farm. Note: The API key is shown only once and is distinct from the API ID. Generate API key.
  3. In Terminal: export TESTING_FARM_API_TOKEN=<TOKEN>
  4. Search: Find the appropriate nightly build and architecture from the latest datagrepper message (e.g., x86_64 or aarch64).
  5. In Terminal (Reserve Machine): Use the following command as an example: testing-farm request --sanity --compose Fedora-Cloud-Base-AmazonEC2.x86_64-Rawhide-20251119.0 --arch x86_64 --reserve

Openstack[edit]

  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[edit]

  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[edit]

Milestone Test Case EC2 (KVM) EC2 (Xen) Local (Optional) Openstack (Optional) Azure (Optional)
Basic QA:Testcase_base_startup
Bot Pass pass psklenar
none
Bot Pass pass coconut
none
none
Basic QA:Testcase_base_reboot_unmount
Bot Pass pass psklenar
none
Bot Pass pass coconut
none
none
Basic QA:Testcase_base_system_logging
Bot Pass pass psklenar
none
Bot Pass pass coconut
none
none
Basic QA:Testcase_base_update_cli
none
none
Bot Pass pass coconut
none
none
Basic / Beta QA:Testcase_package_install_remove
Bot Pass pass psklenar
none
Bot Pass pass coconut
none
none
Basic / Final QA:Testcase_base_artwork_release_identification
Bot Pass pass psklenar
none
none
none
none
Final QA:Testcase_base_edition_self_identification
Bot Pass pass psklenar
none
none
none
none
Final QA:Testcase_base_services_start
Bot Pass pass psklenar
none
Bot Pass pass coconut
none
none
Final QA:Testcase_base_selinux
Bot Pass pass psklenar
[1][2]
none
Bot Pass pass coconut
none
none
Final QA:Testcase_base_service_manipulation
Bot Pass pass psklenar
none
Bot Pass pass coconut
none
none
  1. ↑ https://artifacts.dev.testing-farm.io/a841f592-f746-406e-af06-49a1ea92938a
  2. ↑ daily results https://forge.fedoraproject.org/quality/fmf-tests/src/branch/results/results/reports.md

aarch64[edit]

Milestone Test Case EC2 (KVM) Local (Optional) Openstack (Optional)
Basic QA:Testcase_base_startup
Bot Pass pass psklenar
Bot Pass pass coconut
none
Basic QA:Testcase_base_reboot_unmount
Bot Pass pass psklenar
Bot Pass pass coconut
none
Basic QA:Testcase_base_system_logging
Bot Pass pass psklenar
Bot Pass pass coconut
none
Basic QA:Testcase_base_update_cli
none
Bot Pass pass coconut
none
Basic / Beta QA:Testcase_package_install_remove
Bot Pass pass psklenar
Bot Pass pass coconut
none
Basic / Final QA:Testcase_base_artwork_release_identification
Bot Pass pass psklenar
none
none
Final QA:Testcase_base_edition_self_identification
Bot Pass pass psklenar
none
none
Final QA:Testcase_base_services_start
Bot Pass pass psklenar
Bot Pass pass coconut
none
Final QA:Testcase_base_selinux
Bot Pass pass psklenar
[1][2]
Bot Pass pass coconut
none
Final QA:Testcase_base_service_manipulation
Bot Pass pass psklenar
Bot Pass pass coconut
none
  1. ↑ https://artifacts.dev.testing-farm.io/daee165f-c823-44df-825b-fae504f04f40
  2. ↑ daily results https://forge.fedoraproject.org/quality/fmf-tests/src/branch/results/results/reports.md
Retrieved from "https://fedoraproject.org/w/index.php?title=Test_Results:Fedora_45_Rawhide_20260505.n.0_Cloud&oldid=771467"