Oracle Cloud Infrastructure Documentation

Troubleshooting OpenShift Container Platform on OCI

Use this section to identify and resolve common issues when deploying OpenShift clusters. on OCI.

Not Authorized to Provision Infrastructure

Condition: You receive "not authorized" error in the Resource Manager service when creating infrastructure resources using the Assisted Installer, or when manually creating resources using the Agent-based Installer.

Cause: You don't have the required IAM policies or permissions.

Remedy:

  1. For Assisted Installer, ensure that you have the policies discussed in Securing Resource Manager and Details for Resource Manager.
  2. For Agent-based Installer, ensure you have the permissions to create and manage the resources listed in the OCI Resources for the Agent-based Installer for Manual Installation topic.
  3. For both installation methods, review Managing Access to Resources.
  4. Contact your tenancy administrator if you don't administer IAM permissions.
SSH Failure for Cluster Node Access

Condition: You cannot establish an SSH connection with a cluster node.

Cause: Several issues discussed in Troubleshooting the SSH Connection can prevent an SSH connection to your node.

Remedy: Review the Troubleshooting the SSH Connection topic for detailed steps to diagnose and resolve the issues.
"Insufficient" Error When Adding Node in OpenShift Console

Condition: Red Hat Hybrid Cloud console displays an "Insufficient" error message while adding nodes in OpenShift Console.

Cause: If the domain name generated during node creation isn't valid, the Red Hat Hybrid Cloud console displays an "Insufficient" error message, as shown in the following image:


An image of the OpenShift cluster details page in the Red Hat console.

Note

The error described in this section might occur while you're adding hosts to a cluster in the OpenShift Hybrid Cloud Console, as detailed in Add hosts to a cluster in the OpenShift web console.

Remedy:

To resolve this error, do the following:

  1. Select the link named set the IP or domain used to reach the cluster. Then update the prefix of domain name to api-int from api. For example, if the string displayed is api.addnode1234multiad.my.company.com, edit the prefix section of the string as follows: api-int.addnode1234multiad.my.company.com.
  2. After you update the string, the Update button is enabled. Select the Update button to continue. The nodes' status changes to ready.
    An image of the Update cluster hostname dialog.


    An image of the Update cluster hostname dialog after the string has been edited.

Cluster Installation Fails Due to Missing Tags

Condition: The cluster fails to install or behaves unexpectedly after running the create-cluster stack.

Cause: The required tag stack (create-resource-attribution-tags) wasn't run before running the create-cluster stack.

Remedy: Before installing the cluster on OCI, download and run the create-resource-attribution-tags-vX.X.X.zip stack from the OpenShift on OCI Releases page on GitHub. This stack creates a tag namespace and associated defined-tags (openshift-tags and openshift-resource) that are essential for all subsequent stacks to function correctly. The create-resource-attribution-tags stack only needs to be run once. If the tag namespace and defined-tags are already created, you can directly proceed with cluster installation.