From Fedora Project Wiki
m (Update with 20180410.n.1)
m (Update docker containers tests)
Line 156: Line 156:
<references/>
<references/>


==== '''Docker''' ====
==== '''Docker Container Base''' ====


{| class="wikitable sortable collapsible" border="1" width=100%
{| class="wikitable sortable collapsible" border="1" width=100%
Line 177: Line 177:
| {{result|none}}
| {{result|none}}
| style="background:lightgrey;"|
| style="background:lightgrey;"|
| {{result|none}}<ref>1: Docker installation on the Fedora 28 VM (packages docker and systemd-container which is required by systemd). 2: loading of the Docker image. 3: Creation of a Docker container based on the image previously loaded. 4: Check a CLI (i.e bash) can be accessed into the container. 5: Check network access by executing a "dnf repolist".</ref>  
| {{result|pass|20180410.n.1 menantea}}<ref>1: Docker installation on the Fedora 28 VM (packages docker and systemd-container which is required by systemd). 2: loading of the Docker image. 3: Creation of a Docker container based on the image previously loaded. 4: Check a CLI (i.e bash) can be accessed into the container. 5: Check network access by executing a "dnf update" and try a "dnf install httpd". 6: check container info with "docker info" and "docker ps -a"</ref>
| style="background:lightgrey;"|
| {{result|none}}
| style="background:lightgrey;"|
| {{result|none}}
|-
|}
<references/></onlyinclude>
 
==== '''Docker Container Minimal Base''' ====
 
{| class="wikitable sortable collapsible" border="1" width=100%
|-
! rowspan="2" style="width:10em" | Milestone
! rowspan="2" style="width:10em" | Test Case
! colspan="2" | Bare Metal
! colspan="2" | PKVM BE
! colspan="2" | PKVM LE
! colspan="2" | PVM
|-
! BE !! LE
! Guest BE !! Guest LE
! Guest BE !! Guest LE
! LPAR BE !! LPAR LE
|-
| Optional
| [[QA:Testcase_base_startup]]
| {{result|none}}
| {{result|none}}
| style="background:lightgrey;"|
| {{result|pass|20180410.n.1 menantea}}<ref>1: Docker installation on the Fedora 28 VM (packages docker and systemd-container which is required by systemd). 2: loading of the Docker image. 3: Creation of a Docker container based on the image previously loaded. 4: Check a CLI (i.e bash) can be accessed into the container. 5: Check network access by executing a "microdnf update" and try a "microdnf install httpd". 6: check container info with "docker info" and "docker ps -a"</ref>  
| style="background:lightgrey;"|
| style="background:lightgrey;"|
| {{result|none}}
| {{result|none}}

Revision as of 12:50, 11 April 2018

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 28 20180410.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 i386 ppc64 ppc64le s390x x86_64
Everything boot Download Download Download Download Download Download
Workstation live Download Download
Server dvd Download Download Download Download Download Download Download
Server boot Download Download Download Download Download Download
Cloud_Base vagrant-libvirt Download
Cloud_Base vagrant-virtualbox Download
KDE live Download
Xfce live Download Download
SoaS live Download Download
Mate live Download Download
Cinnamon live Download Download
LXDE live Download Download
Design_suite live Download
Python_Classroom live Download Download
Jam_KDE live Download
AtomicHost vagrant-libvirt Download
LXQt live Download Download
AtomicHost vagrant-virtualbox Download
Security live Download Download
Astronomy_KDE live Download
Scientific_KDE live Download
Python_Classroom vagrant-libvirt Download Download
Robotics live Download
AtomicWorkstation dvd-ostree Download
Python_Classroom vagrant-virtualbox Download Download
Games live Download
Workstation boot Download Download Download
Workstation raw-xz Download Download
Server raw-xz Download Download
Cloud_Base raw-xz Download Download Download Download
Cloud_Base qcow2 Download Download Download Download
Minimal raw-xz Download Download
Xfce raw-xz Download
SoaS raw-xz Download
Container_Base docker Download Download Download Download Download
Python_Classroom raw-xz Download
Container_Minimal_Base docker Download Download Download Download
AtomicHost dvd-ostree Download Download Download
LXQt raw-xz Download
AtomicHost raw-xz Download Download Download
AtomicHost qcow2 Download Download Download

Template:Fedora 28 Branched 20180410.n.1 AMI

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 28 Branched 20180410.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 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

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.

Cloud base

Milestone Test Case Bare Metal PKVM BE PKVM LE PVM
BE LE Guest BE Guest LE Guest BE Guest LE LPAR BE LPAR LE
Basic QA:Testcase_base_startup
none
none
none
none
Pass pass 20180410.n.1 openqa
Pass pass 20180410.n.1 openqa
none
none
Basic QA:Testcase_base_system_logging
none
none
none
none
Pass pass 20180410.n.1 openqa
Pass pass 20180410.n.1 openqa
none
none
Final QA:Testcase_Services_start
none
none
none
none
Pass pass 20180410.n.1 openqa
Pass pass 20180410.n.1 openqa
none
none
Final QA:Testcase_base_selinux
none
none
none
none
Pass pass 20180410.n.1 openqa
Pass pass 20180410.n.1 openqa
none
none
Final QA:Testcase_base_service_manipulation
none
none
none
none
Pass pass 20180410.n.1 openqa
Pass pass 20180410.n.1 openqa
none
none


AtomicHost Local

Milestone Test Case Bare Metal PKVM BE PKVM LE PVM
BE LE Guest BE Guest LE Guest BE Guest LE LPAR BE LPAR LE
Basic QA:Testcase_base_startup
none
none
Pass pass 20180410.n.1 openqa
none
Basic QA:Testcase_base_system_logging
none
none
Pass pass 20180410.n.1 openqa
none
Final QA:Testcase_Services_start
none
none
Pass pass 20180410.n.1 openqa
none
Final QA:Testcase_base_selinux
none
none
Pass pass 20180410.n.1 openqa
none
Final QA:Testcase_base_service_manipulation
none
none
Pass pass 20180410.n.1 openqa
none


Docker Container Base

Milestone Test Case Bare Metal PKVM BE PKVM LE PVM
BE LE Guest BE Guest LE Guest BE Guest LE LPAR BE LPAR LE
Optional QA:Testcase_base_startup
none
none
Pass pass 20180410.n.1 menantea
[1]
none
none
  1. ↑ 1: Docker installation on the Fedora 28 VM (packages docker and systemd-container which is required by systemd). 2: loading of the Docker image. 3: Creation of a Docker container based on the image previously loaded. 4: Check a CLI (i.e bash) can be accessed into the container. 5: Check network access by executing a "dnf update" and try a "dnf install httpd". 6: check container info with "docker info" and "docker ps -a"

Docker Container Minimal Base

Milestone Test Case Bare Metal PKVM BE PKVM LE PVM
BE LE Guest BE Guest LE Guest BE Guest LE LPAR BE LPAR LE
Optional QA:Testcase_base_startup
none
none
Pass pass 20180410.n.1 menantea
[1]
none
none
  1. ↑ 1: Docker installation on the Fedora 28 VM (packages docker and systemd-container which is required by systemd). 2: loading of the Docker image. 3: Creation of a Docker container based on the image previously loaded. 4: Check a CLI (i.e bash) can be accessed into the container. 5: Check network access by executing a "microdnf update" and try a "microdnf install httpd". 6: check container info with "docker info" and "docker ps -a"

Domain joining tests: Active Directory

Milestone Test Case BE LE
Basic QA:Testcase_realmd_join_kickstart
none
none
Basic QA:Testcase_realmd_join_sssd
none
none
Beta QA:Testcase_realmd_join_cockpit
none
none


Domain client tests

Milestone Test Case BE LE
Beta QA:Testcase_domain_client_authenticate (FreeIPA)
Pass pass 20180410.n.1 openqa
Fail fail 20180320.n.0 openqa [1]
Pass pass 20180410.n.1 openqa
Final QA:Testcase_FreeIPA_realmd_login
none
Pass pass 20180410.n.1 openqa
Optional QA:Testcase_domain_client_authenticate (Active Directory)
none
none
  1. ↑ RHBZ #1557609

Release-blocking roles

Single test table
In all of these tests, the test case used is QA:Testcase Server role deploy. That is where the links point. The test must be run for each release-blocking role.
Milestone Test Case Bare Metal PKVM BE PKVM LE PVM
BE LE Guest BE Guest LE Guest BE Guest LE LPAR BE LPAR LE
Basic Domain controller
none
none
none
none
Fail fail 20180410.n.1 openqa [1]
Pass pass 20180410.n.1 openqa
none
none
Basic Database server
none
none
none
none
Pass pass 20180410.n.1 openqa
Pass pass 20180410.n.1 openqa
none
none
  1. ↑ RHBZ #1437793
Domain controller role
Milestone Test Case BE LE
Beta QA:Testcase_FreeIPA_web_ui
none
Pass pass 20180410.n.1 openqa
Beta QA:Testcase_FreeIPA_password_change
none
Pass pass 20180410.n.1 openqa


Database server role

Non-release-blocking roles

Single test table
In all of these tests, the test case used is QA:Testcase Server role deploy. That is where the links point. The test may be run for each non-release-blocking role.
Milestone Test Case BE LE
Beta QA:Testcase_database_server_remote_client
none
Pass pass 20180410.n.1 openqa
Milestone Test Case Bare Metal PKVM BE PKVM LE PVM
BE LE Guest BE Guest LE Guest BE Guest LE LPAR BE LPAR LE
Retrieved from "https://fedoraproject.org/w/index.php?title=Architectures/PowerPC/Fedora_28_PowerPC_Cloud&oldid=515696"