|
2 | 2 | ### Case#1: volume create/delete issue
|
3 | 3 | - locate csi driver pod
|
4 | 4 | ```console
|
5 |
| -$ kubectl get po -o wide -n kube-system | grep csi-blob-controller |
| 5 | +kubectl get po -o wide -n kube-system | grep csi-blob-controller |
| 6 | +``` |
| 7 | +<pre> |
6 | 8 | NAME READY STATUS RESTARTS AGE IP NODE
|
7 | 9 | csi-blob-controller-56bfddd689-dh5tk 4/4 Running 0 35s 10.240.0.19 k8s-agentpool-22533604-0
|
8 | 10 | csi-blob-controller-56bfddd689-sl4ll 4/4 Running 0 35s 10.240.0.23 k8s-agentpool-22533604-1
|
9 |
| -``` |
| 11 | +</pre> |
10 | 12 | - get csi driver logs
|
11 | 13 | ```console
|
12 |
| -$ kubectl logs csi-blob-controller-56bfddd689-dh5tk -c blob -n kube-system > csi-blob-controller.log |
| 14 | +kubectl logs csi-blob-controller-56bfddd689-dh5tk -c blob -n kube-system > csi-blob-controller.log |
13 | 15 | ```
|
14 | 16 | > note: there could be multiple controller pods, logs can be taken from all of them simultaneously, also with `follow` (realtime) mode
|
15 | 17 | > `kubectl logs deploy/csi-blob-controller -c blob -f -n kube-system`
|
16 | 18 |
|
17 | 19 | ### Case#2: volume mount/unmount failed
|
18 | 20 | - locate csi driver pod and make sure which pod do tha actual volume mount/unmount
|
19 | 21 | ```console
|
20 |
| -$ kubectl get po -o wide -n kube-system | grep csi-blob-node |
| 22 | +kubectl get po -o wide -n kube-system | grep csi-blob-node |
| 23 | +``` |
| 24 | +<pre> |
21 | 25 | NAME READY STATUS RESTARTS AGE IP NODE
|
22 | 26 | csi-blob-node-cvgbs 3/3 Running 0 7m4s 10.240.0.35 k8s-agentpool-22533604-1
|
23 | 27 | csi-blob-node-dr4s4 3/3 Running 0 7m4s 10.240.0.4 k8s-agentpool-22533604-0
|
24 |
| -``` |
| 28 | +</pre> |
25 | 29 |
|
26 | 30 | - get csi driver logs
|
27 | 31 | ```console
|
28 |
| -$ kubectl logs csi-blob-node-cvgbs -c blob -n kube-system > csi-blob-node.log |
| 32 | +kubectl logs csi-blob-node-cvgbs -c blob -n kube-system > csi-blob-node.log |
29 | 33 | ```
|
| 34 | +> note: to watch logs in realtime from multiple `csi-blob-node` DaemonSet pods simultaneously, run the command: |
| 35 | +> ```console |
| 36 | +> kubectl logs daemonset/csi-blob-node -c blob -n kube-system -f |
| 37 | +> ``` |
30 | 38 |
|
31 | 39 | ### get blobfuse driver version
|
32 | 40 | ```console
|
33 |
| -# kubectl exec -it csi-blob-node-fmbqw -n kube-system -c blob -- sh |
34 |
| -# blobfuse -v |
35 |
| -blobfuse 1.2.4 |
| 41 | +kubectl exec -it csi-blob-node-fmbqw -n kube-system -c blob -- sh |
| 42 | +blobfuse -v |
36 | 43 | ```
|
| 44 | +<pre> |
| 45 | +blobfuse 1.2.4 |
| 46 | +</pre> |
37 | 47 |
|
38 | 48 | ### check blobfuse mount on the agent node
|
39 | 49 | ```console
|
40 |
| -# mount | grep blobfuse | uniq |
| 50 | +mount | grep blobfuse | uniq |
41 | 51 | ```
|
42 | 52 |
|
43 | 53 | ### troubleshooting connection failure on agent node
|
|
0 commit comments