Failed to install CSV for isf-operator

When you install IBM Fusion, the installation fails with "Failed to install CSV for ifs-operator" error.

For more details, check the log file /home/kni/logs/installoperator_playbook.log.

Diagnosis

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

Open the log file /home/kni/logs/installoperator_playbook.log and search for the string "Wait for CSV isf-operator to get installed" for errors to find the root cause.
If the previous logs do not contain details of the root cause, then continue with next steps for further diagnostics.

Run oc get csv -n ibm-spectrum-fusion-ns on the provisioner (also known as RU7 or compute-1-ru7 node). Example output:

NAME                           DISPLAY              VERSION          REPLACES              PHASE
isf-operator.v2.8.0-13104160   IBM Storage Fusion   2.8.0            isf-operator.v2.7.1   Failed

Check which pods are not in Running or Completed state by using the following command:

oc get pods -n ibm-spectrum-fusion-ns | grep -ivE 'Running|Completed

Sample output with one pod in ImagePullBackOff error:

NAME                                                              READY   STATUS                 RESTARTS   AGE
isf-application-operator-controller-manager-7578464c4b-tld5w      0/2     ImagePullBackOff       0          116m
logcollector-5cf49dbc55-jzczf                                     0/1     Pending                0          116m
logcollector-5cf49dbc55-pjgl5                                     0/1     Pending                0          116m

Run the following describe command to view the details of pod:
```
oc descibe pod <POD NAME> -n ibm-spectrum-fusion-ns
```

Scroll the output and examine the Events section of the output.

Example output:

Events:
  Type     Reason          Age   From               Message
  ----     ------          ----  ----               -------
  Normal   Scheduled       98m   default-scheduler  Error: ImagePullBackOff

If error from the describe command indicates authorisation or authentication error, then check whether the credentials you provided during the stage2 installation are correct.
- For online installation, it is the entitlement key that you provided. In this case, the user is always cp.
- For online installation, also check whether the specified entitlement key includes an IBM Fusion HCI entitlement.
- For installation from enterprise registry, check the provided credentials for your enterprise registry (for both multiple and single repositories).
- Try to pull the image manually on one OpenShift® Container Platform node by connecting to the node from provisioner by using oc debug node/<NODE-NAM>.
If the error from the previous describe command indicates manifest unknown error, then do the following checks:
- For installation from enterprise registry, check whether your enterprise registry is configured properly and reachable from provisooner (RU7).
- For installation from enterprise registry, make sure that the IBM Fusion HCI images are mirrored correctly.
- Make sure that the user mirror images with right digest to right path exist in the enterprise registry.

Next actions

Take corrective actions and click Retry in the installation user interface.