Oracle Cloud Infrastructure Documentation

Troubleshooting OpenShift Container Platform on OCI

Use troubleshooting information to identify and address common issues that can occur while working with OpenShift Container Platform on OCI.

Infrastructure Provisioning Not Authorized

Condition: You get "not authorized" errors in the Resource Manager service when creating infrastructure resources using the Assited Installer, or when creating resources manually as part of the Agent-based Installer work flow.

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

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

Condition: You are unable to make 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 documentation at Troubleshooting the SSH Connection for remedies.
Add node operation fails with "Insufficient" error message in OpenShift Hybrid Cloud 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 To add hosts to a cluster in the OpenShift web console.

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.

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 Failure Due to Missing Tags

Condition: The cluster didn't install or resulted in unexpected behavior after running the create-cluster stack.

Cause: You didn't run the create-resource-attribution-tagsstack before running the create-cluster stack.

Remedy: Before installing an OpenShift 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.