Skip to content

Commit e85fab6

Browse files
authored
Update csi-debug.md
1 parent 6e711cd commit e85fab6

File tree

1 file changed

+6
-4
lines changed

1 file changed

+6
-4
lines changed

docs/csi-debug.md

Lines changed: 6 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,8 @@
11
## CSI driver troubleshooting guide
22
### Case#1: volume create/delete issue
3-
- locate csi driver pod
3+
> This step is not available if you are using [managed CSI driver on AKS](https://docs.microsoft.com/en-us/azure/aks/azure-csi-blob-storage-dynamic).
4+
- find csi driver controller pod
5+
> 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.
46
```console
57
kubectl get po -o wide -n kube-system | grep csi-blob-controller
68
```
@@ -9,12 +11,12 @@ NAME READY STATUS RESTARTS AGE
911
csi-blob-controller-56bfddd689-dh5tk 4/4 Running 0 35s 10.240.0.19 k8s-agentpool-22533604-0
1012
csi-blob-controller-56bfddd689-sl4ll 4/4 Running 0 35s 10.240.0.23 k8s-agentpool-22533604-1
1113
</pre>
12-
- get csi driver logs
14+
15+
- get pod description and logs
1316
```console
17+
kubectl describe pod csi-blob-controller-56bfddd689-dh5tk -n kube-system > csi-blob-controller-description.log
1418
kubectl logs csi-blob-controller-56bfddd689-dh5tk -c blob -n kube-system > csi-blob-controller.log
1519
```
16-
> note: there could be multiple controller pods, logs can be taken from all of them simultaneously, also with `follow` (realtime) mode
17-
> `kubectl logs deploy/csi-blob-controller -c blob -f -n kube-system`
1820

1921
### Case#2: volume mount/unmount failed
2022
- locate csi driver pod and make sure which pod does the actual volume mount/unmount

0 commit comments

Comments
 (0)