Troubleshooting

Inspecting Deployment

Inspect the deployment using Get commands to access basic output, type:

For example

Get the CTE CSI pod names that were deployed on the Kubernetes cluster, type:

kubectl get pods --namespace=kube-system -o wide | grep cte-csi

Response

cte-csi-controller-0      2/2     Running   0      25h    192.168.77.182   ub20-work1    <none>   <none>
cte-csi-node-28srz        4/4     Running   0      25h    192.168.77.181   ub20-work1    <none>   <none>
cte-csi-node-cjzzn        4/4     Running   0      25h    192.168.76.68    ub20-master   <none>   <none>

The logs are split between two containers within the CTE CSI pods. The logs on the cte-csi container contain logs for CSI activity. For example, information such as registration and mounting volumes are contained within these logs. The logs for the cte-agent-logs contain logs for the CTE Fuse encryption engine agent. You can view logs by using the kubectl logs command. Using the output from the example above, you can get the logs for the CTE-CSI container.

After you get the pod name, type the following two commands:

kubectl logs --namespace=kube-system <nodeName> cte-csi
kubectl logs --namespace=kube-system <nodeName> cte-agent-logs

Problems with Registration

If the Registration token is not added, or an incorrect one is added to the yaml file, use the describe pod command to obtain what went wrong to with token.