Red Hat OpenShift Container Platform 4 operator catalog image fails to start with "CrashLoopBackOff"

Solution Unverified - Updated -

Issue

  • The operator catalog image in the project "openshift-marketplace" fails to start with "CrashLoopBackOff" in a disconnected setup.

    shell$ oc get pods -o wide -n openshift-marketplace
    NAME                                   READY   STATUS             RESTARTS   AGE   IP            NODE                            NOMINATED NODE   READINESS GATES
    marketplace-operator-xxxxxxxxx-xxxxx   1/1     Running            0          45m   10.130.0.26   example-dc-xxxxx-master-1       <none>           <none>
    my-operator-catalog-xxxxx              0/1     CrashLoopBackOff   19         52m   10.131.0.4    example-dc-xxxxx-worker-yyyyy   <none>           <none>
    
  • No "packagemanifest" found in the "openshift-marketplace" project after following official documentation to install operator life cycle manager (OLM) in disconnected environments.

    shell$ oc get packagemanifest -n openshift-marketplace
    No resources found in openshift-marketplace namespace.
    
  • No operators available in the operator catalog after following the official documentation to install operator life cycle manager (OLM) in disconnected environments

Environment

  • Red Hat OpenShift Container Platform 4.3

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content