File tree Expand file tree Collapse file tree 1 file changed +6
-4
lines changed Expand file tree Collapse file tree 1 file changed +6
-4
lines changed Original file line number Diff line number Diff line change 1
1
## CSI driver debug tips
2
2
3
3
### case #1 : volume create/delete failed
4
- - locate csi driver pod
4
+ > There could be multiple controller pods (only one pod is the leader), if there are no helpful logs, try to get logs from the leader controller pod.
5
+ - find csi driver controller pod
5
6
``` console
6
7
$ kubectl get pod -o wide -n kube-system | grep csi-nfs-controller
7
8
NAME READY STATUS RESTARTS AGE IP NODE
8
9
csi-nfs-controller-56bfddd689-dh5tk 5/5 Running 0 35s 10.240.0.19 k8s-agentpool-22533604-0
9
10
csi-nfs-controller-56bfddd689-sl4ll 5/5 Running 0 35s 10.240.0.23 k8s-agentpool-22533604-1
10
11
```
11
- - get csi driver logs
12
+ - get pod description and logs
12
13
``` console
14
+ $ kubectl describe csi-nfs-controller-56bfddd689-dh5tk -n kube-system > csi-nfs-controller-description.log
13
15
$ kubectl logs csi-nfs-controller-56bfddd689-dh5tk -c nfs -n kube-system > csi-nfs-controller.log
14
16
```
15
- > note: there could be multiple controller pods, if there are no helpful logs, try to get logs from other controller pods
16
17
17
18
### case #2 : volume mount/unmount failed
18
19
- locate csi driver pod that does the actual volume mount/unmount
@@ -24,8 +25,9 @@ csi-nfs-node-cvgbs 3/3 Running 0 7m4s 1
24
25
csi-nfs-node-dr4s4 3/3 Running 0 7m4s 10.240.0.4 k8s-agentpool-22533604-0
25
26
```
26
27
27
- - get csi driver logs
28
+ - get pod description and logs
28
29
``` console
30
+ $ kubectl describe po csi-nfs-node-cvgbs -n kube-system > csi-nfs-node-description.log
29
31
$ kubectl logs csi-nfs-node-cvgbs -c nfs -n kube-system > csi-nfs-node.log
30
32
```
31
33
You can’t perform that action at this time.
0 commit comments