Troubleshooting Global Data Platform issues
Warning: Do NOT delete IBM Storage Scale pods. Deletion of Scale pods in
many circumstances has implications on availability and data integrity.
Filesystem status from Remote file systems is stuck in Connecting state
- Cause
- The secure boot is not supported by Scale and CNSA.
- Resolution
-
- Check whether the nodes are running with secure
boot:
mokutil --sb-stateSecureBoot enabled
- As a root password, you can disable the secure boot with the following
command:
mokutil --disable-validationpassword length: 8~16 input password: input password again:
- Check whether the nodes are running with secure
boot:
Delay between filesystem mount and IBM Storage Scale Container Storage Interface Driver (CSI) pods deployment
- Diagnosis
- CSI custom resource (CSO) status shows an error in getting the primary filesystem details. Run
the following command to get the status:
Example output:oc describe cso -n ibm-spectrum-scale-csiStatus: Conditions: Last Transition Time: 2023-06-06T07:10:08Z Message: Failed to get the details of the primary filesystem: fs3 Reason: GetFileSystemFailed Status: False Type: Success
- Resolution
- Delete only the CSI operator pod from
ibm-spectrum-scale-csinamespace. For example, operator pod nameibm-spectrum-scale-csi-operator-7bd7f4654d-28h56.Verify whether the CSO status show Success as True. For example:Status: Conditions: Last Transition Time: 2023-06-06T07:11:16Z Message: The CSI driver resources have been created/updated successfully Reason: CSIConfigured Status: True Type: Success
Backup of scale deployed application with static PV fails
- Problem statement
- This is a IBM Storage Scale limitation. Snapshots can be taken only for certain types of IBM Storage Scale volumes. Volume Snapshot is supported only for the independent fileset based PVCs. For more information about the limitation, see IBM Spectrum Scale documentation.
- Resolution
- As a resolution, reconfigure IBM Storage Scale and IBM Storage Scale Container Storage Interface Driver for independent fileset PVCs and try again. For steps to reconfigure, see IBM Spectrum Scale documentation.
Known issues
- If you deployed IBM Fusion to any custom namespace, the log collection package appears under the folder name ibm-spectrum-fusion-namespace. Instead, it must be under the custom namespace that is used in actual log collection.