Unity CSI driver not creating volume on Unity

Hi Gurus,

- I'm setting up kubernetes cluster, and following https://dell.github.io/storage-plugin-docs/docs/installation/helm/unity/, to install CSI driver for unity.

- I'm able to get the pods running:

[root@master test]# kubectl get po -n unity
NAME READY STATUS RESTARTS AGE
snapshot-controller-0 1/1 Running 2 4d15h
unity-controller-69f859885b-hnhzk 5/5 Running 15 131m
unity-node-n9bjd 2/2 Running 2 131m
unity-node-xmgmc 2/2 Running 2 131m

- I'm able to specify the storageclass in myvalyes.yaml file, and created storageclasses:

[root@master test]# kubectl get storageclasses
NAME PROVISIONER RECLAIMPOLICY VOLUMEBINDINGMODE ALLOWVOLUMEEXPANSION AGE
unity-iscsi csi-unity.dellemc.com Retain WaitForFirstConsumer true 135m
unity-nfs csi-unity.dellemc.com Retain WaitForFirstConsumer true 135m

 

- I tried to create a pvc as below, but i cannot see the request send to Unity storage in controller pods:

[root@master test]# cat pvc.json
kind: PersistentVolumeClaim
apiVersion: v1
metadata:
name: pvol1
# namespace: test-unity
spec:
accessModes:
- ReadWriteOnce
volumeMode: Filesystem
resources:
requests:
storage: 25Gi
storageClassName: unity-iscsi

[root@master test]# kubectl create -f pvc.json

- I'm expecting the PVC will dynamically create the volume on unity, but actually, there's no event happened

[root@master ~]# kubectl logs -f unity-controller-69f859885b-hnhzk -c driver -n unity

 

- Now, PVC is created but due to no volume created, it's left in pending state.

[root@master test]# kubectl get pvc -A
NAMESPACE NAME STATUS VOLUME CAPACITY ACCESS MODES STORAGECLASS AGE
default pvol1 Pending unity-iscsi 30s

 

- I thought after the PVC has the storageclass field specified, the volume will be provisioned dynamically, but it doesn't happen in my case. 

 

How to troubleshoot this ? 

 

Thanks in advance.

 

 

B/R

Jason