Chapter 5. Software policies
Chapter 5. Software policies 5.1. Test Suite versions Red Hat recommends that the latest version of the test suite packages be used for all testing. When a new version of any test suite package is made available, test results created using the versions will continue to be accepted for a period of three months. At the end of this period results from these versions will automatically be rejected and testing will need to be repeated with the later test suite packages. Note The current valid package versions are displayed on the results package submission form. 5.2. Red Hat Enterprise Linux versions The latest minor release of Red Hat Enterprise Linux (RHEL) version is always recommended; however, any release that satisfies the full testing criteria may be used. Testing on the earliest fully-supported release will maximize the potential customer base. If multiple minor releases are used during testing, the newest minor release will be used as the posted release for the model. Depending on the features of a given model a minimum release may be required other than what is desired. Important Instance Type that are available without certified images are required to be installed and tested using the GA media (or equivalent) without additional errata. The test suite is tested against RHEL 8 and RHEL 9 Base OS server installations. All the variants of the RHEL major version share a common core set of packages, and the use of these variants is allowed during certification testing. However, the variants may only provide a subset of the required packages that may result in the need for retesting with the Base OS variant. Important Technical assistance during certification is not offered when using these variants. 5.3. Unmodified Red Hat software The Red Hat CCSP Instance Type certification requires testing on a standard installation of Red Hat Enterprise Linux without any modifications. Changes to the default configuration presented by the installer and first boot utilities are allowed when the configuration change can be made using one of the standard system tools and when the default configuration does not create the potential for data loss. Required changes to the default configuration must be documented in a Red Hat Knowledge Base Solution that is associated with the certification listing. Additionally, the Red Hat certification test suite should not be modified. The test suite will perform a self check and will fail the supportable test if modified. 5.4. Kernel Boot parameters Additional kernel parameters may be utilized if they Are used to correct hardware configuration Do not disable functionality Do not expose a potential for data loss when not in use Example if the kernel parameter noacpi is required to boot a system which does not install without that parameter, this would likely be acceptable. If, however, the system would install but corrupts data over time when noacpi is not specified, the certification would be suspended until the situation is resolved. Additional kernel parameters utilized during certification are documented in Red Hat Knowledge Base Solution associated with the certification listing. 5.5. SELinux Certifications must be run with SELinux enabled using the Targeted Policy and with Enforcing on. The test suite will check for these conditions.