| Test Results:Fedora 38 Branched 20230323.n.0 Cloud | 您所在的位置：网站首页 › 房价跌落最新信息新闻 › Test Results:Fedora 38 Branched 20230323.n.0 Cloud |
|
This page records Cloud validation testing test results for the Fedora 38 20230323.n.0 nightly compose. Contents 1 Which tests to run 2 How to test 3 x86_64 hvm standard AMIs 4 x86_64 hvm gp2 AMIs 5 arm64 hvm standard AMIs 6 arm64 hvm gp2 AMIs 7 Results summary page 8 Add, Modify or Remove a Test Case 9 Key 10 Test Matrix 10.1 Cloud Provider Setup 10.1.1 x86_64 10.1.2 aarch64 Which tests to run[edit] Test coverage pageThis 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 Download Server dvd Download Download Download Download Server boot 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 Container_Minimal_Base docker Download Download Download Download Kinoite dvd-ostree 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 Sericea dvd-ostree Download Server_KVM qcow2 Download Download Download Download Silverblue dvd-ostree Download Download LXQt live Download Download Budgie live Download Sway live Download i3 live 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 Python_Classroom raw-xz Download LXQt raw-xz Download Phosh raw-xz Download x86_64 hvm standard AMIs[edit] Region AMI ID Direct launch link ap-northeast-1 ami-07f69c372a6528abe Launch in EC2 ap-northeast-2 ami-0fd34583eb4dd9ad6 Launch in EC2 ap-south-1 ami-071903a960f9a4745 Launch in EC2 ap-southeast-1 ami-078d95fe71a82b353 Launch in EC2 ap-southeast-2 ami-02d43b88cccb15617 Launch in EC2 ca-central-1 ami-05423b6db0d070475 Launch in EC2 eu-central-1 ami-09ccf633adabb55bb Launch in EC2 eu-west-1 ami-0f6467e0cb5f931ea Launch in EC2 eu-west-2 ami-024fd4775554dc227 Launch in EC2 sa-east-1 ami-09f0a5da2ba1f78a1 Launch in EC2 us-east-1 ami-09108adb75f1ac0c4 Launch in EC2 us-east-2 ami-0dd016f7a3dc6726e Launch in EC2 us-west-1 ami-09b565c0745f1cba2 Launch in EC2 us-west-2 ami-0d12b27159799723f Launch in EC2 x86_64 hvm gp2 AMIs[edit] Region AMI ID Direct launch link ap-northeast-1 ami-06160a4751e359740 Launch in EC2 ap-northeast-2 ami-070c5b56cce68b013 Launch in EC2 ap-south-1 ami-0e369009118b1e832 Launch in EC2 ap-southeast-1 ami-0338a3b5080fb57cb Launch in EC2 ap-southeast-2 ami-06a306df1e19fcc2a Launch in EC2 ca-central-1 ami-063f9ff1b5ea074d7 Launch in EC2 eu-central-1 ami-0dbee58e2a918d5e0 Launch in EC2 eu-west-1 ami-002051f045bd5b15a Launch in EC2 eu-west-2 ami-0ef3444e058a3ae46 Launch in EC2 sa-east-1 ami-0639a90f623c5c9ce Launch in EC2 us-east-1 ami-02b85396456836ddc Launch in EC2 us-east-2 ami-01dca2973acac8abf Launch in EC2 us-west-1 ami-06c69d0e24cf39b9d Launch in EC2 us-west-2 ami-0b4c138b180819b3c Launch in EC2 arm64 hvm standard AMIs[edit] Region AMI ID Direct launch link ap-northeast-1 ami-080dee4f0590c1412 Launch in EC2 ap-northeast-2 ami-0384c80c72f106163 Launch in EC2 ap-south-1 ami-080568cd95d9de99c Launch in EC2 ap-southeast-1 ami-0bfda7b26e37d4917 Launch in EC2 ap-southeast-2 ami-0dcbca80b3cc73efc Launch in EC2 ca-central-1 ami-0f00c7dcc9b8f4956 Launch in EC2 eu-central-1 ami-0c3b5d207ef83dd1d Launch in EC2 eu-west-1 ami-09bfbcc20e7c39a64 Launch in EC2 eu-west-2 ami-0e29db2ed42fdd85f Launch in EC2 sa-east-1 ami-0f29c4ff539ca2161 Launch in EC2 us-east-1 ami-04f3a4b31971c8cb5 Launch in EC2 us-east-2 ami-0073a44a7639d6444 Launch in EC2 us-west-1 ami-0528cb119c54ae470 Launch in EC2 us-west-2 ami-04432c8642a47b403 Launch in EC2 arm64 hvm gp2 AMIs[edit] Region AMI ID Direct launch link ap-northeast-1 ami-05654efc92aecb52c Launch in EC2 ap-northeast-2 ami-0f369b4b2c6336c0a Launch in EC2 ap-south-1 ami-0d7bc31cbbdf051c6 Launch in EC2 ap-southeast-1 ami-0843733eb01e06fd6 Launch in EC2 ap-southeast-2 ami-059a6a07bff6ad579 Launch in EC2 ca-central-1 ami-0d3e71800da9bdf48 Launch in EC2 eu-central-1 ami-020c1e5e72f86c29e Launch in EC2 eu-west-1 ami-0dd8cb9d7f417214a Launch in EC2 eu-west-2 ami-0c759360193f4d9f6 Launch in EC2 sa-east-1 ami-027eaf0b65f54a997 Launch in EC2 us-east-1 ami-0be33871da90f1827 Launch in EC2 us-east-2 ami-037cd0476abcf9044 Launch in EC2 us-west-1 ami-0ca01996b89640910 Launch in EC2 us-west-2 ami-0d5b66e54b6439614 Launch in EC22. 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 updatesDon'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 testingIn 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 38 Branched 20230323.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] 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[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 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}} Brief description about the warning status pass hongqing warn kparal Multiple results - More people can easily provide results to a single test case. {{result|pass|hongqing}} {{result|warn|kparal}} pass previous run Result from previous test run - This test result is directly moved from the test run of previous . {{result|pass|previous 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 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 testAmazon 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 imageLocal 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. x86_64[edit] 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 noneaarch64[edit] 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 |
| CopyRight 2018-2019 实验室设备网 版权所有 |