supportable test

The supportable test gathers basic host information. You can run this test to verify that system components like the kernel, RPM packages, and hardware comply with certification requirements.

What the test covers
RHEL version supported
  • RHEL 8
  • RHEL 9
  • RHEL 10 The supportable test gathers basic information about the host under test (HUT). Red Hat uses this information to verify that the system complies with the certification requisites.
What the test does

The test has several subtests that perform the following tasks:

  1. Confirm that the /proc/sys/kernel/tainted file contains a zero (0), which indicates that the kernel is not tainted.
  2. Confirm that package verification with the rpm -V command shows that no files have been modified.
  3. Confirm that the rpm -qa kernel command shows that the buildhost of the kernel package is a Red Hat server.
  4. Record the boot parameters from the /proc/cmdline file.
  5. Confirm that the`rpm -V redhat-certification` command shows that no modifications have been made to any of the certification test suite files.
  6. Confirm that all the modules shown by the lsmod command show up in a listing of the kernel files with the rpm -ql kernel command.
  7. Confirm that all modules are on the Kernel Application Binary Interface (kABI) stablelist.
  8. Confirm that the module vendor and buildhost are appropriate Red Hat entries.
  9. Confirm that the kernel is the GA kernel of the Red Hat minor release. The subtest tries to verify the kernel with data from the redhat-certification package. If the kernel is not present, the subtest attempts to verify the kernel by using the Internet connection. To verify the kernel by using the Internet connection, configure the HUT’s routing and DNS resolution to access the Internet. Alternatively, set the ftp_proxy=http://proxy.domain:80 environment variable.
  10. Check for any known hardware vulnerabilities reported by the kernel. The subtest reads the files in the /sys/devices/system/cpu/vulnerabilities/ directory and exits with a warning if the files contain the word “Vulnerable”.
  11. Confirm if the system has any offline CPUs by checking the output of the lscpu command.
  12. Confirm if Simultaneous Multithreading (SMT) is available, enabled, and active in the system.
  13. Check if there is unmaintained hardware or drivers in systems running RHEL 8 or later. Unmaintained hardware and drivers are no longer tested or updated on a routine basis. Red Hat may fix serious issues, including security issues, but you cannot expect updates on any planned cadence. Replace or remove unmaintained hardware or drivers as soon as possible.
  14. Check if there is deprecated hardware or drivers in systems running RHEL 8 or later. Deprecated hardware and drivers are still tested and maintained. They are planned to become unmaintained and eventually disabled in a future release. Replace or remove deprecated devices or hardware as soon as possible.
  15. Check if there is disabled hardware in systems running RHEL 8 or later. RHEL cannot use disabled hardware. Replace or remove the disabled hardware from your system before running the test again.
  16. Run the following checks on the software RPM packages:
    • Check the RPM build host information to isolate non-Red Hat packages. The test asks you to explain the reasons for including the non-Red Hat packages. Red Hat reviews the reasons and approve or reject each package individually.
    • Check that the installed RPM packages are from the Red Hat products available in the offering and have not been modified. Red Hat reviews verification failures in the rpm_verification_report.log file. You need to reinstall the failed packages and rerun the test.
  17. Check the presence of both Red Hat and non-Red Hat firmware files in the system. It lists the non-Red Hat files, if present, and exits with REVIEW status.
  18. Check the page size of systems by getconf PAGESIZE command.
  19. For RHEL AI certification, the supportable test runs an additional test that captures the following details of the HUT :
    1. OS version
    2. Total number of AI accelerators in the systems
    3. The list of driver modules that are loaded. After performing these tasks, the test gathers a sosreport and the output of the dmidecode command.
  20. If in-kernel Intel QuickAssist Technology (QAT) devices are present:
    • The test checks basic driver health using the kernel sysfs-driver-qat ABI (qat/state, cfg_services, num_rps when present).
    • It scans dmesg for known QAT firmware or acceleration load failure patterns. Systems without QAT exposed in sysfs, skip the check as not applicable. This is not a cryptographic or compression performance test.
Running the test

The rhcert tool runs the supportable test automatically as part of every run of the test suite. The supportable test runs before any other test. The output of the supportable test is required as part of the test suite logs. Red Hat will reject test logs that do not contain the output of the supportable test. Use the following command to run the test manually, if required:

$ rhcert-cli run --test supportable
Run time
The supportable test takes around 1 minute on a reference workstation. This system is a 2013-era, single CPU, 3.3GHz, 6-core or 12-thread Intel machine with 8 GB of RAM. The system runs Red Hat Enterprise Linux 6.4, AMD64, and Intel 64, and was installed using the Kickstart files in this guide.

The time varies depending on the speed of the machine and the number of RPM files that are installed.