Common issues

Use this troubleshooting information to resolve common install and upgrade problems related to IBM Storage Fusion services.

Common known issues in installation

  • If you find an error saying Configmap fusionplatform not found in fusion namespace in the preparer operator logs, then the error does not have any impact and can be ignored from the isf-prereq-operator-controller-manager-xxxx pod logs

Troubleshooting common installation issues

ImagePull failure during installation or upgrade of any service
If an ImagePull failure occurs during the installation or upgrade of the any service, then restart the pod and retry. If the issue persists, contact IBM support.
Rook-cephfs pods are in CrashLoopBackOff off state
Data Cataloging and Backup & Restore services that are installed, go into degraded state, and rook-ceph-mds-ocs-storagecluster pods are in CrashLoopBackOff state.
Follow the steps to resolve the issue:
  1. If IBM Storage Fusion is installed with OpenShift® Container Platform or Data Foundation v4.10.x, then you can upgrade it to v4.11.x.
  2. The upgrade of OpenShift Container Platformor Data Foundation from v4.10.x to v4.11.x resolves the CrashLoopBackOff error in rook-ceph-mds-ocs-storagecluster pods and get it to running state. Eventually services also go to healthy state.
    Note: Also, you can upgrade OpenShift Container Platform or Data Foundation to further versions supported by IBM Storage Fusion.
Whenever the upgrade button is unavailable for any service
During the offline upgrade, if you do not see the upgrade button for any of the services after upgrading IBM Storage Fusion operator, then check the catalogsource pod, and it should be in a running state. For any imagepullbackoff error, ensure you have completed mirroring and updated imagecontentsourcepolicy.