Debugging initialization issues

This section outlines how to debug IBM Spectrum Scale Container Storage Interface driver initialization issues.

Issue: IBM Spectrum Scale Container Storage Interface driver pod goes in an error state during deployment

# kubectl get pod -n ibm-spectrum-scale-csi-driver

NAME                                       READY   STATUS             RESTARTS   AGE
ibm-spectrum-scale-csi-attacher-0          1/1     Running            0          4d2h
ibm-spectrum-scale-csi-attacher-1          1/1     Running            0          4d2h
ibm-spectrum-scale-csi-dxslh               0/3     Error              20         4d2h
ibm-spectrum-scale-csi-provisioner-0       1/1     Running            0.         4d2h
ibm-spectrum-scale-csi-resizer-0           1/1     Running            0          4d2h
ibm-spectrum-scale-csi-snapshotter-0       1/1     Running            0          4d2h

How to troubleshoot?

Look for the IBM Spectrum Scale Container Storage Interface driver container logs in the IBM Spectrum Scale Container Storage Interface driver pod as shown in the following example, where you can see the root cause of the failure.

# kubectl logs ibm-spectrum-scale-csi-dxslh ibm-spectrum-scale-csi

E1017 06:13:07.529701       1 gpfs.go:252] Error getting cluster ID: rpc error: code =
Unauthenticated desc = Unauthorized GET request to https://ip-10-0-73-
79.ec2.internal:443/scalemgmt/v2/cluster: 401 Unauthorized
E1017 06:13:07.529711       1 gpfs.go:196] Error in plugin initialization: rpc error: code =
Unauthenticated desc = Unauthorized GET request to https://ip-10-0-73-
79.ec2.internal:443/scalemgmt/v2/cluster: 401 Unauthorized
F1017 06:13:07.529719       1 main.go:65] Failed to initialize Scale CSI Driver: rpc error: code 
= Unauthenticated desc = Unauthorized GET request to https://ip-10-0-73-
79.ec2.internal:443/scalemgmt/v2/cluster: 401 Unauthorized

The logs indicate that the credentials that are used to fetch the cluster ID from IBM Spectrum Scale GUI are incorrect. To fix the problem, ensure that the secrets used during deployment are correct. For more information, see Changing the configuration after deployment.