Red Hat SummitEste conteúdo não está disponível no idioma selecionado.
Chapter 9. IPI certification tests
The IPI test validates whether the Host Under Test (HUT) can be controlled, accessed, deployed, and rebooted remotely by using the Red Hat OpenShift Container Platform ironic service and the HUT’s bare metal management controller (BMC).
The test runs in a container accessible by the node that is running the ironic service.
Supported RHOCP versions - RHOCP 4.17, 4.18 and 4.19.
The test plan consists of the following tests:
9.1. Self check test
The self-check test confirms that all required software packages for certification are installed and unaltered, ensuring the test environment is ready for certification. Certification packages must not be modified for testing or any other purpose.
Success Criteria
The test environment includes all necessary certification packages and the packages have not been modified.
9.2. IPI test
The IPI test automates power management of the server from the OpenShift console through the ironic service to the BMC.
The test runs the following subtest:
9.2.1. Check and update power state subtest
The check_update_power_state subtest first checks if the HUT is powered on, and then restarts the HUT.
The subtest monitors the status of the HUT node every 15 seconds, for a maximum of 15 minutes.
Success Criteria
- The HUT restarts successfully in less than 15 minutes.
9.3. Openshift IPI test
The installer-provisioned infrastructure (IPI) test automates power management of the server from the OpenShift console through the ironic service to the BMC.
The test runs the following subtests:
9.3.1. MustGather validation subtest
The must-gather validation subtest collects system and diagnostic information, such as configuration details, system logs, and other relevant OpenShift cluster information. It is essential for debugging issues in the HUT.
This subtest takes approximately 10 minutes to gather all the required data of the HUT.
Success Criteria
The test generates a must-gather report and stores it at the location /etc/redhat-certification/openshift with a success message, for example:
Success: Must-gather collected and stored at /etc/redhat-certification/openshift
Success: Must-gather collected and stored at /etc/redhat-certification/openshift9.3.2. CoreOS validation subtest
The CoreOS validation subtest performs the following functions:
- Checks the CoreOS version available in the OpenShift cluster of your HUT.
- Verifies if the Red Hat CoreOS (RHCOS) version from the node matches the RHCOS Version from the OpenShift release.
Success Criteria
Displays the CoreOS version of the Red Hat OpenShift cluster and reports any discrepancies if the RHCOS version doesn’t match, for example,
Success: Found CoreOS version: 417.94.202411261220 Success: RHCOS version matches OpenShift release. No discrepancies found. PASS
Success: Found CoreOS version: 417.94.202411261220
Success: RHCOS version matches OpenShift release. No discrepancies found.
PASS9.3.3. Workload validation subtest
The workload validation subtest deploys a workload on a specified node, monitors the CPU usage and checks the impact on the workload based on the CPU utilization.
The subtest performs the following tasks:
Before test execution:
- Checks if the pod already exists. If it exists, it deletes the existing pod.
- Starts a new pod and deploys the workload on the selected node.
-
After successful deployment, it displays a success message
Workload is successfully deployed and running.
During the test execution:
-
Verifies and reports the workload status as
RunningorSuccess.
-
Verifies and reports the workload status as
After the test execution:
- Deletes the pod and cleans up the workload on the node.
- Evaluates and reports the CPU usage before, during and after running the test.
Success Criteria
Generates workload-test.yaml for the selected node, monitors and displays the CPU usage before, during and after the test execution, for example:
9.3.4. IPI validation subtest
The IPI validation subtest checks the following operations:
- If the OpenShift cluster on your node is deployed by using IPI.
- If the bare-metal operator is healthy.
Success Criteria
Displays a success message which includes the following:
- Confirmation about deploying your cluster by using IPI.
- The health status of your bare-metal operator, for example:
Success: Baremetal operator is functioning as expected with all status conditions in a healthy state. Success: Cluster appears to be deployed using IPI. PASS
Success: Baremetal operator is functioning as expected with all status conditions in a healthy state.
Success: Cluster appears to be deployed using IPI.
PASS9.3.5. BMCTest validation subtest
The BMCtest validation subtest checks the BMC control and the Redfish boot capabilities of the OpenShift cluster on the OpenShift bare-metal nodes.
Success Criteria
Displays a success message along with the BMC test summary after the test completes, for example:
'%20d='M201.5%20305.5c-13.8%200-24.9-11.1-24.9-24.6%200-13.8%2011.1-24.9%2024.9-24.9%2013.6%200%2024.6%2011.1%2024.6%2024.9%200%2013.6-11.1%2024.6-24.6%2024.6zM504%20256c0%20137-111%20248-248%20248S8%20393%208%20256%20119%208%20256%208s248%20111%20248%20248zm-132.3-41.2c-9.4%200-17.7%203.9-23.8%2010-22.4-15.5-52.6-25.5-86.1-26.6l17.4-78.3%2055.4%2012.5c0%2013.6%2011.1%2024.6%2024.6%2024.6%2013.8%200%2024.9-11.3%2024.9-24.9s-11.1-24.9-24.9-24.9c-9.7%200-18%205.8-22.1%2013.8l-61.2-13.6c-3-.8-6.1%201.4-6.9%204.4l-19.1%2086.4c-33.2%201.4-63.1%2011.3-85.5%2026.8-6.1-6.4-14.7-10.2-24.1-10.2-34.9%200-46.3%2046.9-14.4%2062.8-1.1%205-1.7%2010.2-1.7%2015.5%200%2052.6%2059.2%2095.2%20132%2095.2%2073.1%200%20132.3-42.6%20132.3-95.2%200-5.3-.6-10.8-1.9-15.8%2031.3-16%2019.8-62.5-14.9-62.5zM302.8%20331c-18.2%2018.2-76.1%2017.9-93.6%200-2.2-2.2-6.1-2.2-8.3%200-2.5%202.5-2.5%206.4%200%208.6%2022.8%2022.8%2087.3%2022.8%20110.2%200%202.5-2.2%202.5-6.1%200-8.6-2.2-2.2-6.1-2.2-8.3%200zm7.7-75c-13.6%200-24.6%2011.1-24.6%2024.9%200%2013.6%2011.1%2024.6%2024.6%2024.6%2013.8%200%2024.9-11.1%2024.9-24.6%200-13.8-11-24.9-24.9-24.9z'/%3e%3c/svg%3e){kind=small}