The catlogsource pod for Red Hat operators is not running

The catlogsource pod for redhat-operators is not running in openshift-marketplace namespace. Check the log file %s for more details.

Diagnosis

Run all commands as a kni user from the provisioner node (also known as RU7 or compute-1-ru7).

Run the following command to verify whether the catalogsource exists or not.
```
oc -n openshift-marketplace get catsrc
```

Verify whether the catalog source with name redhat-operators exists.

Sample output:

NAME                   DISPLAY                       TYPE   PUBLISHER   AGE
certified-operators    Certified Operators           grpc   Red Hat     3d22h
community-operators    Community Operators           grpc   Red Hat     3d22h
ibm-operator-catalog   IBM Operator Catalog          grpc   IBM         3d12h
isf-catalog            IBM Spectrum Fusion Catalog   grpc   IBM         3d21h
opencloud-operators    IBMCS Operators               grpc   IBM         3d12h
redhat-marketplace     Red Hat Marketplace           grpc   Red Hat     3d22h
redhat-operators       Red Hat Operators             grpc   Red Hat     3d22h

If the catalog source exists, then run the following command to check for catalogsource pod:
```
oc -n openshift-marketplace get po
```

Check whether a pod that starts with redhat-operators- exists with the Status as Running and Ready as 1/1.

Example:

NAME                                    READY   STATUS    RESTARTS   AGE
certified-operators-2j2jx               1/1     Running   0          3d11h
community-operators-9wxcp               1/1     Running   0          14h
ibm-operator-catalog-d768c              1/1     Running   0          3d10h
isf-catalog-d972s                       1/1     Running   0          3d21h
marketplace-operator-84558d7577-9nmdj   1/1     Running   0          3d21h
opencloud-operators-bghhj               1/1     Running   0          3d12h
redhat-marketplace-czb2z                1/1     Running   0          3d21h
redhat-operators-49nf8                  1/1     Running   0          142m

If the pod is in ImagePullBackOff or ErrImagePull state, then describe pod to check the exact reason:
- If describe shows timeout in pulling image, then check the network bandwidth.
- If error listed is the image manifest is not known and it is an offline installation, then check whether the image is present in enterprise registry.
- If describe shows authentication error and it is an offline installation, then check the secret pull-secret in namespace openshift-config for correct enterprise registry credentials.

Next actions

Take corrective actions and rerun installation.