ibm-cp-security-operator CSV was not created

If the ibm-cp-security-operator cluster service version (CSV) was not created, you cannot complete an installation or upgrade.

Symptoms

The ibm-cp-security-operator CSV was not created.

Diagnosing the problem

If you are installing QRadar® Suite Software in an online environment, check that the IBM® operator catalog source pod is running in the openshift-marketplace by typing the following command.
```
oc get pod -lolm.catalogSource=ibm-operator-catalog -n openshift-marketplace
```
If you are installing QRadar Suite Software in an air-gapped environment, check that the catalog sources are running by typing the following command.
```
oc get pod  -n openshift-marketplace | grep -E "couchdb|redis|opencloud|elasticsearch|cp4s"
```

Check for failed pods or jobs in the openshift-marketplace namespace by typing the following command.

oc get pod -n openshift-marketplace | grep -Ev "Running|Completed" && oc get job -n openshift-marketplace | grep -Ev "1/1|Completed"

Validate that the QRadar Suite Software subscription is created by typing the following command.
```
oc get subscription ibm-cp-security-operator  -n <cp4s_namespace>
```

Check the openshift-operator-lifecycle-manager catalog and olm operator logs for errors by typing the following commands.

oc logs -lapp=catalog-operator -n openshift-operator-lifecycle-manager  --tail 200 |grep -E "error|level=warning|Failed"

oc logs -lapp=olm-operator -n openshift-operator-lifecycle-manager  --tail 200

Resolving the problem

If the result from step 1 shows that the catalog source is not running, describe the IBM operator catalog source pod by typing the following command.
```
oc describe pod  -lolm.catalogSource=ibm-operator-catalog -n openshift-marketplace
```
If the result from step 2 shows that the catalog source is not running, validate that the QRadar Suite Software images were mirrored correctly to the local docker registry by checking your local docker registry.

If the openshift-operator-lifecycle-manager catalog operator logs show errors similar to the following error,

'Warning' reason: 'ResolutionFailed' constraints not satisfiable: no operators found matching the criteria of subscription ibm-cp-security-operator, subscription ibm-cp-security-operator exists

then restart the IBM operator catalog source and the openshift-operator-lifecycle-manager catalog operator pod by typing the following command.

oc delete pod  -lolm.catalogSource=ibm-operator-catalog -n openshift-marketplace && \
  oc delete pod -lapp=catalog-operator -n openshift-operator-lifecycle-manager