Ce contenu n'est pas disponible dans la langue sélectionnée.

Chapter 10. Creating a RHOCP Bare Metal supplemental certification


The Red Hat OpenShift Bare Metal Certification is a supplemental certification. It might have already been created for you as part of the Red Hat Enterprise Linux System certification.

If it was not automatically created for you, or if you need to apply for the certification at a later date, perform the following steps:

Prerequisites

  • Your server must have already earned the following certifications:

    • Red Hat Enterprise Linux System
    • Red Hat OpenShift Container Platform

You must create individual supplemental certifications for each type, IPI or AI. However, if you intend to certify both IPI and AI, create a single supplemental certification request.

For more information about creating the Red Hat OpenShift Container Platform layered certification, see Certifying layered products.

Procedure

  1. Log in to the Red Hat Partner Connect portal.
  2. Click the Red Hat Enterprise Linux System certification that is related to the assisted installer certification you want to open.
  3. Click the Related Certifications tab on the upper left side of the table.
  4. Click the Red Hat OpenShift Container Platform certification that is related to the assisted installer certification you want to open.
  5. Click the Related Certifications tab on the upper left side of the table.
  6. At the top of the certifications table, click Add Related Certification.

    The Create Related Certification window appears.

  7. Select Supplemental and click Next.
  8. Review the certification information and click Open.

    The supplemental certification is created.

  9. Leave a comment to the Red Hat certification team to specify that you want either or both of the following components added to the test plan:

    • Bare Metal Management
    • Assisted Installer
  10. After you get the new test plan, start testing.

10.1. Running the IPI test

The installer-provisioned infrastructure (IPI) test validates whether your BMC-capable bare-metal nodes can be accessed, deployed, and rebooted on an established RHOCP environment.

The test uses the Ironic service already running on the RHOCP environment to provision the bare-metal node undergoing certification.

Prerequisites

Important

The test must validate that the server can be turned on and off remotely. When creating the bmh.yaml file for the bare-metal node, set the online field to false. For example:

apiVersion: metal3.io/v1alpha1
kind: BareMetalHost
metadata:
  name: openshift-worker-<num>
spec:
  online: false
Copy to Clipboard Toggle word wrap

Failure to set this field appropriately will cause the test to fail.

Procedure

  1. Identify the IP address of the node where the Ironic service is running. For example:

    # oc -n openshift-machine-api get pods -o wide | egrep -v ‘image|controller|operator’
    
    NAME                                              READY   STATUS    RESTARTS   AGE   IP             NODE
    metal3-78b556db65-lgkrp                    7/7     Running   0          12d   172.22.0.111   worker-0
    Copy to Clipboard Toggle word wrap

    The metal3 pod runs the Ironic service that the test uses to install the bare-metal node undergoing certification. Make a note of its IP address; this is the Ironic API endpoint that you will use in a later step.

  2. Get the credentials of the Ironic service and make a note of them. You will use them in a later step.

    # oc -n openshift-machine-api get secret/metal3-ironic-password -o template --template '{{.data.username}}' | base64 -d
    
    # oc -n openshift-machine-api get secret/metal3-ironic-password -o template --template '{{.data.password}}' | base64 -d
    Copy to Clipboard Toggle word wrap
  3. Log in to any cluster node. For example:

    # oc debug host/master-0
    Copy to Clipboard Toggle word wrap
  4. Prepare the node to run the certification test:

    1. Install podman if it is not already installed.
    2. Create the /tmp/results directory. The test will store the results in this directory

      Note

      The node must have access to the baremetal and the provisioning networks if both are available on the RHOCP environment. If you only configured the baremetal network, the node must be connected to it.

    3. Log in to the Red Hat Certification image registry:

      # podman login registry.redhat.io
      Username: <registry_service_account_username>
      Password: <registry_service_account_password>
      Login Succeeded!
      Copy to Clipboard Toggle word wrap
    4. Download the redhat-certification-baremetal image from the Red Hat catalog:

      # podman pull registry.redhat.io/rhcertification/redhat-certification-baremetal
      Copy to Clipboard Toggle word wrap
  5. Run the IPI test:

    # podman run -it --net host -v /tmp/results:/var/rhcert_results:Z redhat-certification-baremetal
    Copy to Clipboard Toggle word wrap
    Expand
    Table 10.1. IPI test parameter description
    ParameterDescription

    -it

    Starts an interactive session.

    --net host

    Podman uses the network stack of the host for the container. The network configuration of the container is the same as that of the host. The container shares the same service ports that are available to the host.

    -v tmp/results:/var/rhcert_results

    Allows mounting the content of a host folder /tmp/results to /var/rhcert_results.

    :Z

    Ensures you have read and write permissions on the mount point.

  6. Enter the username, password, and the URL of the Ironic service that you acquired before. The URL must be in the format https://<Ironic_IP_address>:6385.
  7. Select the bare-metal node on which you want to run the test.

    The UUID, Name, Power State, and Provision State of the selected node displays. The test will start after you select the node.

  8. Confirm whether the bare-metal node is powered on when prompted. After you confirm this, the test restarts the bare-metal node.

    Test result files are generated at /tmp/results.

  9. At the Red Hat certification website, submit the results to the supplemental RHOCP certification for your server.

10.2. Running the OpenShift IPI test

The OpenShift installer-provisioned infrastructure (IPI) test validates whether you can access, deploy and reboot your BMC-capable bare-metal nodes on an established RHOCP environment.

The test uses the ironic service already running on the RHOCP environment to provision the bare-metal node undergoing certification.

Prerequisites

Ensure to meet following prerequisites before proceeding with the certification:

  • A Controller system that has access to an IPI cluster.
  • A bare-metal node in which you run all the tests is called the host under test (HUT).

Figure 10.1. OpenShift IPI test environment

On the Controller system:

  • You have installed the following packages:

    • redhat-certification
    • redhat-certification-openshift
    • redhat-certification-bmc
  • You have stored your pull secret at the location /opt/dev-scripts/pull_secret.json.
  • Ensure to have the kubeconfig file. You can either export it as an environment variable or provide it during the test run time by using the following command: export KUBECONFIG=/root/full/path/kubeconfig
  • From the Extra Packages for Enterprise Linux (EPEL) repository, find and install the parallel package.
  • Locate and configure the files install-config.yaml and clouds.yaml with their specific environment details. You can find them at the location /etc/redhat-certification/openshift/.
  • You have the installer-provisioned cluster (HUT) ready.

On the HUT:

Procedure

  1. Identify the IP address of the node where the Ironic service is running. For example:

    # oc -n openshift-machine-api get pods -o wide | egrep -v ‘image|controller|operator’
    
    NAME                                              READY   STATUS    RESTARTS   AGE   IP             NODE
    metal3-78b556db65-lgkrp                    7/7     Running   0          12d   172.22.0.111   worker-0
    Copy to Clipboard Toggle word wrap
  2. The metal3 pod runs the Ironic service that the test uses to install the bare-metal node undergoing certification. Note its IP address; this is the Ironic API endpoint that you will use in a later step.
  3. Run the following command to plan and run the OpenShift_IPI test on your HUT:

    $ rhcert-cli plan
    $ rhcert-cli run --test openshift_ipi
    Copy to Clipboard Toggle word wrap

    IPI test runs the following subtests:

    • MustGather validation - collects the system and diagnostic information, such as configuration details, system logs, and other relevant data of your OpenShift cluster. It is essential for debugging issues.
    • CoreOS validation - checks the CoreOs version available in the OpenShift cluster and validates it against an official Red Hat release.
    • Workload validation - deploys a workload on a specified node, monitors CPU usage, and checks workload impact based on CPU utilization.
    • IPI validation - checks if the OpenShift cluster is deployed by using IPI.
    • BMCTest validation - tests the BMC control and the Redfish boot capabilities of the OpenShift cluster on the OpenShift bare-metal nodes.
  4. At the Red Hat certification website, submit the results to the supplemental RHOCP certification for your server.
  5. Also, upload the must-gather tar.bz file located at the default location /etc/redhat-certification/openshift/ by using the following command:

    $ rhcert-cli upload --certification-id 123456 --description "Anything about the file" --file /etc/redhat-certification/openshift/must-gather.local.123456.tar.gz
    Copy to Clipboard Toggle word wrap

10.3. Running the assisted installer test

The assisted installer tests verify that your bare-metal servers can be installed by using the assisted installer for OpenShift Container Platform.

The tests are for bare-metal servers only. VMs are not supported.

Important

If you prefer using Cockpit instead of the command line for Assisted Installer certification testing, you must set up the Cockpit first. See Configuring the systems and running tests by using Cockpit for instructions.

Prerequisites

Procedure

  1. Log in to the single-node cluster.
  2. Install the following redhat-certification packages:

    • redhat-certification
    • redhat-certification-openshift

      For example:

      # dnf install redhat-certification redhat-certification-openshift
      Copy to Clipboard Toggle word wrap
  3. In the Red Hat Hybrid Cloud Console, generate an OpenShift Manager API token.
  4. Add the token to the OFFLINE_TOKEN variable and export it.

    For example,

    # export OFFLINE_TOKEN=<value_of_your_token>
    Copy to Clipboard Toggle word wrap
  5. Confirm if the cluster is accessible by using the following command:

    # oc status
    Copy to Clipboard Toggle word wrap
  6. Run the tests according to test plan:

    # rhcert-run
    Copy to Clipboard Toggle word wrap

    The similar set of tests get displayed as follows:

    Alternatively, you can use rhcert-cli to run the test as follows:

    # rhcert-cli plan
    Copy to Clipboard Toggle word wrap
    # rhcert-cli run –test assisted_installer
    Copy to Clipboard Toggle word wrap

    Save the test result:

    # rhcert-cli save
    Copy to Clipboard Toggle word wrap
  7. Submit the results of both tests to the supplemental RHOCP certification for your server at the Red Hat Certification website.
Retour au début
Red Hat logoGithubredditYoutubeTwitter

Apprendre

Essayez, achetez et vendez

Communautés

À propos de la documentation Red Hat

Nous aidons les utilisateurs de Red Hat à innover et à atteindre leurs objectifs grâce à nos produits et services avec un contenu auquel ils peuvent faire confiance. Découvrez nos récentes mises à jour.

Rendre l’open source plus inclusif

Red Hat s'engage à remplacer le langage problématique dans notre code, notre documentation et nos propriétés Web. Pour plus de détails, consultez le Blog Red Hat.

À propos de Red Hat

Nous proposons des solutions renforcées qui facilitent le travail des entreprises sur plusieurs plates-formes et environnements, du centre de données central à la périphérie du réseau.

Theme

© 2025 Red Hat