Catalog source pod is healthy

Message: IBM Fusion catalog source pod is not found or is not healthy.

Diagnostics

Note: Run all commands as a kni user from the provisioner node.

Run the following command to verify whether the catalogsource exists or not.

oc -n openshift-marketplace get catsrc

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

From the output, check for catalog source with name isf-catalog exists.

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

Check for a pod that starts with isf-catalog- and is in Running state with 1/1 containers in READY field.

For example

oc -n openshift-marketplace get po

Sample output:

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 network bandwidth.
- Offline installation:
  - If the listed error is related to an image manifest not known, then check whether the image is present in the enterprise registry.
  - If describe shows authentication error, then check whether the secret pull-secret in namespace openshift-configs has the correct credentials for the enterprise registry.

Next actions

Take corrective measures based on the diagnostics and rerun the installation.