Chapter 10. Troubleshooting common installation problems

If you are experiencing difficulties installing the Red Hat OpenShift Data Science Add-on, read this section to understand what could be causing the problem, and how to resolve the problem.

If you cannot see the problem here or in the release notes, contact Red Hat Support.

10.1. The OpenShift Data Science operator cannot be retrieved from the image registry

Problem

When attempting to retrieve the OpenShift Data Science operator from the image registry, an Failure to pull from quay error message appears. The OpenShift Data Science 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 Dedicated for further information about the Failure to pull from quay error message.

Resolution

  • To resolve this issue, contact Red Hat support.

10.2. OpenShift Data Science cannot be installed due to insufficient cluster resources

Problem

When attempting to install OpenShift Data Science, an error message appears stating that installation prerequisites have not been met.

Diagnosis

  1. Log in to OpenShift Cluster Manager (https://console.redhat.com/openshift/).

  2. Click Clusters.

    The Clusters page opens.

  3. Click the name of the cluster you want to install OpenShift Data Science on.

    The Details page for the cluster opens.

  4. Click the Add-ons tab and locate the Red Hat OpenShift Data Science card.
  5. Click Install. The Configure Red Hat OpenShift Data Science pane appears.
  6. If the installation fails, click the Prerequisites tab.
  7. Note down the error message. If the error message states that you require a new machine pool, or that more resources are required, take the appropriate action to resolve the problem.

Resolution

10.3. The dedicated-admins Role-based access control (RBAC) policy cannot be created

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 Dedicated web console, change into 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.

    The Pod details page appears.

  5. Click Logs.
  6. Select rhods-deployer 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.

10.4. OpenShift Data Science does not install on unsupported infrastructure

Problem

Customer deploying on an environment not documented as being supported by the RHODS operator.

Diagnosis

  1. In the OpenShift Dedicated web console, change into 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.

    The Pod details page appears.

  5. Click Logs.
  6. Select rhods-deployer 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 Data Science. For more information, see Requirements for OpenShift Data Science.

10.5. The creation of the OpenShift Data Science Custom Resource (CR) fails

Problem

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

Diagnosis

  1. In the OpenShift Dedicated web console, change into 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.

    The Pod details page appears.

  5. Click Logs.
  6. Select rhods-deployer 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.

10.6. The creation of the OpenShift Data Science Notebooks Custom Resource (CR) fails

Problem

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

Diagnosis

  1. In the OpenShift Dedicated web console, change into 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.

    The Pod details page appears.

  5. Click Logs.
  6. Select rhods-deployer 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.7. The Dead Man’s Snitch operator’s secret does not get created

Problem

An issue with Managed Tenants SRE automation process causes the Dead Man’s Snitch operator’s secret to not get created.

Diagnosis

  1. In the OpenShift Dedicated web console, change into 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.

    The Pod details page appears.

  5. Click Logs.
  6. Select rhods-deployer from the drop-down list
  7. Check the log for the ERROR: Dead Man Snitch secret does not exist. error message.

Resolution

Contact Red Hat support.

10.8. The PagerDuty secret does not get created

Problem

An issue with Managed Tenants SRE automation process causes the PagerDuty’s secret to not get created.

Diagnosis

  1. In the OpenShift Dedicated web console, change into 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.

    The Pod details page appears.

  5. Click Logs.
  6. Select rhods-deployer from the drop-down list
  7. Check the log for the ERROR: Pagerduty secret does not exist error message.

Resolution

Contact Red Hat support.

10.9. The SMTP secret does not exist

Problem

An issue with Managed Tenants SRE automation process causes the SMTP secret to not get created.

Diagnosis

  1. In the OpenShift Dedicated web console, change into 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.

    The Pod details page appears.

  5. Click Logs.
  6. Select rhods-deployer from the drop-down list
  7. Check the log for the ERROR: SMTP secret does not exist error message.

Resolution

Contact Red Hat support.

10.10. The ODH parameter secret does not get created

Problem

An issue with the OpenShift Data Science add-on’s flow could result in the ODH parameter secret to not get created.

Diagnosis

  1. In the OpenShift Dedicated web console, change into 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.

    The Pod details page appears.

  5. Click Logs.
  6. Select rhods-deployer 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.