Chapter 3. Supportability

3.1. Supportability Overview

The Supportability tests, also known as cloud/supportable, ensure that the image is supportable by Red Hat. The test confirms that the image consists of Red Hat kernel and user space software, is run in a Red Hat supportable environment, and includes access to Red Hat updates and fixes.

The cloud/supportable tests include the following subtests:

3.2. Kernel

The Kernel subtest confirms the kernel that the image is running is from Red Hat, is appropriate and supported for the version of RHEL undergoing certification, and has not been modified. The kernel version may be the original General Availability (GA) version or any subsequent kernel errata released for the RHEL major + minor release. For more information on Red Hat Enterprise Linux Life Cycle and Kernel Versions, refer to Red Hat Enterprise Linux Life Cycle and Red Hat Enterprise Linux Release Dates.

The kernel subtest also ensures that the kernel is not tainted when running in the environment. For more information about kernel tainting, refer to Why is the kernel "tainted" and how are the taint values deciphered?.

Success Criteria:

  • The running kernel is a Red Hat kernel.
  • The running kernel is released by Red Hat for use with the RHEL version.
  • The running kernel is not tainted.

3.3. Kernel Modules

The Kernel Modules subtest confirms the loaded kernel modules are from Red Hat, either from the running kernel’s package or a Red Hat Driver Update (see Where can I download Driver Update Program (DUP) disks?). The kernel module subtest also ensures the kernel modules do not identify as Technology Preview when running in the environment (see What does a "Technology Preview" feature mean?).

Success Criteria:

The kernel modules are from Red Hat and supported.

3.4. Unsupported Hardware

Confirms that the Red Hat kernel has not identified unsupported hardware. This prevents customer production risks which arise from running Red Hat products on unsupported configurations and environments. The kernel is aware of hardware that is not considered supportable for a variety of reasons. When the kernel identifies such hardware, it will either provide an unsupported hardware message in the system logs or trigger a kernel taint.

It is recommended to install and run RHEL on certified hardware. For a complete list of hardware certified for RHEL 6 and RHEL 7, refer to Red Hat Ecosystem Catalog.

Success Criteria:

The kernel does not identify unsupported hardware.

3.5. Architecture

The Architecture subtest confirms that the host architecture displayed in the RHEL image is supported by RHEL, the CCSP program, and the kernel. Currently, for RHEL 6 the CCSP Image Certification is provided on x86, x86_64, ppc, ppc64 architectures, and for RHEL 7 it is provided on x86_64, ppc, ppc64, ppc64le architectures. This test also ensures that the platform is on the supported hypervisor.

Success Criteria:

  • The PASS scenarios of architecture/hypervisor for RHEL 6 is x86 (i386 packages with i686 kernel), and x86_64 on RHEL KVM, VMware, and HyperV. It also includes ppc and ppc64 on PowerVM.
  • The PASS scenarios of architecture/hypervisor for RHEL 7 is x86_64 on RHEL KVM, VMware, and HyperV. It also includes ppc and ppc64 on PowerVM; ppc64le on BareMetal, PowerVM, and RHEV for Power.

3.6. Root Filesystem

Confirms that the root filesystem type and minimum size of an image follow the guidelines for each RHEL release. This ensures that the image has a reasonable amount of space required to operate effectively, run applications, and install upgrades for customer use. The root file system type is prescribed per RHEL major release.

Success Criteria:

  • RHEL 6: The root file system for RHEL 6.x is 6GB or greater on an ext4 or ext3 formatted partition.
  • RHEL 7: The root file system for RHEL 7.x is 10GB or greater on an xfs or ext4 formatted partition.

3.7. Installed RPMs

Confirms that RPM packages installed on the system are from Red Hat and not modified, potentially enabling customers to avoid the significant risks arising from unexpected software/packages, further ensuring that customers are starting with a supportable environment.

Non-Red Hat packages may be installed if they are necessary to enable the cloud environment, but they are acceptable where they are documented and if they DO NOT modify or conflict with Red Hat packages/software. This subtest will require detailed review at Red Hat to confirm success or failure if non Red Hat packages are installed.

For more information on Red Hat support policies on third-party software, refer to https://access.redhat.com/support/offerings/production/soc.

Success Criteria:

  • The installed Red Hat provided RPM packages are from Red Hat product(s) available in the offering.
  • The installed Red Hat RPM packages are not modified.
  • The installed Non-Red Hat RPM packages are necessary to enable the cloud environment and are documented.
  • The installed Non Red Hat RPM packages do not conflict with Red Hat provided packages/software available in Red Hat products included in the offering.

3.8. Software Repositories

Confirms that relevant Red Hat repositories are configured and GPG keys are already imported on the image to avoid potential significant risks from unsupported content. Red Hat provides core software packages/content in Red Hat official software repositories (included with attached subscriptions) which are signed with GPG keys to ensure authenticity of the distributed files. Software provided as part of these repositories is fully supported and reliable for customer production environments. For more information, refer to Production Support Scope of Coverage.

Repositories published but not supported by Red Hat, such as EPEL or the RHEL Supplementary and Optional , and non-Red Hat repositories may be configured if they are necessary to enable the cloud environment but they must be properly described and approved.

Success Criteria:

  • Supported Red Hat repositories are configured.
  • GPG keys for Red Hat repositories are already imported in the image.
  • Red Hat repositories configured on the image match the image content.
  • Non-Red Hat repositories if required for proper operation of the cloud are configured and described.