Log collection

Use the CSI (Container Storage Interface) driver logs for problem identification.

Note: These procedures are applicable for both Kubernetes and Red Hat OpenShift. For Red Hat OpenShift, replace kubectl with oc in all relevant commands.

To collect and display logs, related to the different components of IBM block storage CSI driver, use the following Kubernetes commands:

Log collection for CSI pods, daemonset, and StatefulSet

$> kubectl get all -n <namespace>  -l csi

For example:

$> kubectl get all -n <namespace> -l csi
NAME READY STATUS RESTARTS AGE
pod/ibm-block-csi-controller-0 4/4 Running 0 2h
pod/ibm-block-csi-node-nbtsg 3/3 Running 0 2h
pod/ibm-block-csi-node-wd5tm 3/3 Running 0 2h
pod/ibm-block-csi-operator-7684549698-hzmfh 1/1 Running 0 2h

NAME DESIRED CURRENT READY UP-TO-DATE AVAILABLE NODE SELECTOR AGE
daemonset.apps/ibm-block-csi-node 2 2 2 2 2 <none> 2h

NAME DESIRED CURRENT UP-TO-DATE AVAILABLE AGE
deployment.apps/ibm-block-csi-operator 1 1 1 1 2h

NAME DESIRED CURRENT READY AGE
replicaset.apps/ibm-block-csi-operator-7684549698 1 1 1 2h

NAME DESIRED CURRENT AGE
statefulset.apps/ibm-block-csi-controller 1 1 2h

Log collection for IBM block storage CSI driver controller

$> kubectl log -f -n <namespace> ibm-block-csi-controller-0 -c ibm-block-csi-controller

Log collection for IBM block storage CSI driver node (per worker node or PODID)

$> kubectl log -f -n <namespace> ibm-block-csi-node-<PODID> -c ibm-block-csi-node

Log collection for Operator for IBM block storage CSI driver

$> kubectl log -f -n <namespace> ibm-block-csi-operator-<PODID> -c ibm-block-csi-operator