SupportConsoleDevelopersStart a trialContact

Chapter 10. Troubleshooting common installation problems

If you are experiencing difficulties installing the Red Hat OpenShift AI Operator, read this section to understand what could be causing the problem and how to resolve it.

If the problem is not included here or in the release notes, contact Red Hat Support. When opening a support case, it is helpful to include debugging information about your cluster.

You can collect this information by using the must-gather tool as described in Must-Gather for Red Hat OpenShift AI and Gathering data about your cluster.

You can also adjust the log level of OpenShift AI Operator components to increase or reduce log verbosity to suit your use case. For more information, see Configuring the OpenShift AI Operator logger.

Problem

On OpenShift 4.21 and later, clicking Install on Operators such as the Node Feature Discovery (NFD) Operator or the NVIDIA GPU Operator in OperatorHub redirects to a ClusterExtensions page instead of the standard installation flow. This occurs because OLMv1 catalog is enabled by default as a Technology Preview feature on OpenShift 4.21+.

When OLMv1 is enabled, the following behavior occurs:

  • You must manually create ClusterExtension custom resources using YAML to install Operators through OLMv1.
  • OpenShift AI and dependency Operators installed using CSV-based OLMv0 do not appear under Ecosystem Installed Operators, although oc get csv lists them correctly.

Diagnosis

  1. In the OpenShift web console, navigate to Operators OperatorHub.
  2. Search for "Node Feature Discovery" or "NVIDIA GPU Operator".
  3. Click the Operator tile and then click Install.
  4. If you are redirected to a ClusterExtensions page instead of the standard installation form, OLMv1 catalog is enabled.

Resolution

Disable the OLMv1 catalog to restore the standard installation experience for dependency Operators. Choose one of the following methods:

Method 1: User Preferences

  1. In the OpenShift web console, click your username in the upper-right corner.
  2. Select User Preferences.
  3. Under OLMv1 Catalog, clear the Enable OLMv1 catalog checkbox.
  4. Return to Operators OperatorHub and install the Operator, such as the Node Feature Discovery (NFD) or NVIDIA GPU, using the standard installation flow.

Method 2: Software Catalog filter

  1. In the OpenShift web console, navigate to Operators OperatorHub.
  2. Under Types on the left sidebar, click Operators.
  3. Clear the Enable OLMv1 Tech Preview checkbox.
  4. Install the Operator, such as the Node Feature Discovery (NFD) or NVIDIA GPU, using the standard installation flow.

After disabling OLMv1, the Operators install using CSV-based OLMv0, and appear correctly in Operators Installed Operators.

Note

To view Operators installed using OLMv0 while OLMv1 is enabled, access the legacy view directly at /k8s/ns/<_namespace_>/clusterserviceversions, replacing <namespace> with the Operator namespace such as openshift-nfd or nvidia-gpu-operator.

Problem

When attempting to retrieve the Red Hat OpenShift AI Operator from the image registry, an Failure to pull from quay error message appears. The Red Hat OpenShift AI Operator might be unavailable for retrieval in the following circumstances:

  • The image registry is unavailable.
  • There is a problem with your network connection.
  • Your cluster is not operational and is therefore unable to retrieve the image registry.

Diagnosis

Check the logs in the Events section in OpenShift for further information about the Failure to pull from quay error message.

Resolution

  • Contact Red Hat support.

Problem

You are deploying on an environment that is not documented as supported by the Red Hat OpenShift AI Operator.

Diagnosis

  1. In the OpenShift web console, switch to the Administrator perspective.
  2. Click Workloads Pods.
  3. Set the Project to All Projects or redhat-ods-operator.

  4. Click the rhods-operator-<random string> pod that shows an error in the Status column.

    The Pod details page appears.

  5. Click Logs.
  6. Select rhods-operator from the drop-down list.
  7. Check the log for the ERROR: Deploying on $infrastructure, which is not supported. Failing Installation error message.

Resolution

  • Before proceeding with a new installation, ensure that you have a fully supported environment on which to install OpenShift AI. For more information, see Supported Configurations for 3.x.

Problem

During the installation process, the OpenShift AI Custom Resource (CR) does not get created. This issue occurs in unknown circumstances.

Diagnosis

  1. In the OpenShift web console, switch to the Administrator perspective.
  2. Click Workloads Pods.
  3. Set the Project to All Projects or redhat-ods-operator.

  4. Click the rhods-operator-<random string> pod that shows an error in the Status column.

    The Pod details page appears.

  5. Click Logs.
  6. Select rhods-operator from the drop-down list.
  7. Check the log for the ERROR: Attempt to create the ODH CR failed. error message.

Resolution

  • Contact Red Hat support.

Problem

During the installation process, the OpenShift AI Notebooks Custom Resource (CR) does not get created. This issue occurs in unknown circumstances.

Diagnosis

  1. In the OpenShift web console, switch to the Administrator perspective.
  2. Click Workloads Pods.
  3. Set the Project to All Projects or redhat-ods-operator.

  4. Click the rhods-operator-<random string> pod that shows an error in the Status column.

    The Pod details page appears.

  5. Click Logs.
  6. Select rhods-operator from the drop-down list.
  7. Check the log for the ERROR: Attempt to create the RHODS Notebooks CR failed. error message.

Resolution

  • Contact Red Hat support.

10.6. The OpenShift AI dashboard is not accessible
Copy link

Problem

After installing OpenShift AI, the redhat-ods-applications, redhat-ods-monitoring, and redhat-ods-operator project namespaces are Active but you cannot access the dashboard due to an error in one of the pods.

Diagnosis

  1. In the OpenShift web console, switch to the Administrator perspective.
  2. Click Workloads Pods.
  3. Set the Project to All Projects.

  4. Click Filter and select the checkbox for every status except Running and Completed.

    The page displays the pods that have an error.

Resolution

  • To see more information and troubleshooting steps for a pod, on the Pods page, click the link in the Status column for the pod.
  • If the Status column does not display a link, click the pod name to open the pod details page and then click the Logs tab.

Problem

After uninstalling the OpenShift AI Operator and reinstalling it by using the CLI, the reinstallation fails with an unable to find DSCInitialization error in one of the OpenShift AI Operator pod logs. This issue can occur if the Auth custom resource from the previous installation was not deleted after uninstalling the OpenShift AI Operator and before reinstalling it. For more information, see Understanding the uninstallation process.

Diagnosis

  1. In the OpenShift web console, switch to the Administrator perspective.
  2. Click Workloads Pods.
  3. Set the Project to All Projects or redhat-ods-operator.

  4. Click the rhods-operator-<random string> pod that shows an error in the Status column.

    The Pod details page appears.

  5. Click Logs.
  6. Select rhods-operator from the drop-down list.

  7. Check the log for an error message similar to the following: 

    {"name":"auth"},"namespace":"","name":"auth","reconcileID":"7bff53ae-1252-46fe-831a-fdc824078a1b","error":"unable to find DSCInitialization","stacktrace":"sigs.k8s.io/controller-runtime/pkg/internal/controller.

Resolution

  1. Uninstall the OpenShift AI Operator.

  2. Delete the Auth custom resource:

    1. In the OpenShift web console, switch to the Administrator perspective.
    2. Click API Explorer.
    3. From the All groups drop-down list, select or enter services.platform.opendatahub.io.
    4. Click the Auth kind.
    5. Click the Instances tab.

    6. Click the action menu (⋮) and select Delete Auth.

      The Delete Auth dialog appears.

    7. Click Delete.
  3. Install the OpenShift AI Operator again.

Problem

The Role-based access control (RBAC) policy for the dedicated-admins group in the target project cannot be created. This issue occurs in unknown circumstances.

Diagnosis

  1. In the OpenShift web console, switch to the Administrator perspective.
  2. Click Workloads Pods.
  3. Set the Project to All Projects or redhat-ods-operator.

  4. Click the rhods-operator-<random string> pod that shows an error in the Status column.

    The Pod details page appears.

  5. Click Logs.
  6. Select rhods-operator from the drop-down list.
  7. Check the log for the ERROR: Attempt to create the RBAC policy for dedicated admins group in $target_project failed. error message.

Resolution

  • Contact Red Hat support.

Problem

An issue with the OpenShift AI Operator’s flow could result in failure to create the ODH parameter.

Diagnosis

  1. In the OpenShift web console, switch to the Administrator perspective.
  2. Click Workloads Pods.
  3. Set the Project to All Projects or redhat-ods-operator.

  4. Click the rhods-operator-<random string> pod that shows an error in the Status column.

    The Pod details page appears.

  5. Click Logs.
  6. Select rhods-operator from the drop-down list.
  7. Check the log for the ERROR: Addon managed odh parameter secret does not exist. error message.

Resolution

  • Contact Red Hat support.
Red Hat logoGithubredditYoutubeTwitter

Learn

Try, buy, & sell

Communities

About Red Hat

We deliver hardened solutions that make it easier for enterprises to work across platforms and environments, from the core datacenter to the network edge.

Making open source more inclusive

Red Hat is committed to replacing problematic language in our code, documentation, and web properties. For more details, see the Red Hat Blog.

About Red Hat Documentation

We help Red Hat users innovate and achieve their goals with our products and services with content they can trust. Explore our recent updates.

Legal Notice

Theme

© 2026 Red HatBack to top