Start a Conversation

Unsolved

S

1 Message

3218

March 3rd, 2020 10:00

CSI Driver for Unity VSA - unity-node problems

I have a working Unity VSA running in VM Ware Workstation (test platform). It is successfully providing storage to pods running in CoreOS based Kubernetes cluster.

I have download and installed the CSI drivers from the git repo (https://github.com/dell/csi-unity/tree/v1.0.0) following the instructions and using Helm to create the necessary unity-controller-0 and unity-node- pods.

The unity-controller-0 pod is reliably running, authenticates with the VSA and the logs contain no errors.

The unity-node pods initally come up as Running, but within seconds their state changes to Error and then CrashLoopBackOff. This cycle repeats continually.

Looking at the logs with 'kubectl logs unity-node-k5k5h -n unity -c driver' I see the following:

Endpoint unix:///var/lib/kubelet/plugins/unity.emc.dell.com/csi_sock
ls: cannot access /var/lib/kubelet/plugins/unity.emc.dell.com/csi_sock: No such file or directory
gounity logger initiated. This should be called only once.
csi-unity logger initiated. This should be called only once.
time="2020-03-02T23:41:18Z" level=info msg="X_CSI_MODE:node"
time="2020-03-02T23:41:18Z" level=info msg="X_CSI_UNITY_NODENAME:node05"
time="2020-03-02T23:41:18Z" level=info msg="configured csi-unity.dellemc.com" autoprobe=false endpoint="https://10.0.1.50" insecure=true mode=node nodename=node05 password="******" pvtMountDir=/var/lib/kubelet/plugins/unity.emc.dell.com/disks systemname= user=admin
time="2020-03-02T23:41:18Z" level=info msg="identity service registered"
time="2020-03-02T23:41:18Z" level=info msg="node service registered"
time="2020-03-02T23:41:18Z" level=info msg=serving endpoint="unix:///var/lib/kubelet/plugins/unity.emc.dell.com/csi_sock"
time="2020-03-02T23:41:18Z" level=info msg="Executing NodeGetInfo. Host name:node05"
time="2020-03-02T23:41:18Z" level=info msg="AutoProbe has not been called. Executing manual probe"
time="2020-03-02T23:41:18Z" level=info msg="Executing nodeProbe"
time="2020-03-02T23:41:18Z" level=info msg="Executing Authenticate REST client"
time="2020-03-02T23:41:21Z" level=info msg="Response code:200 for url: /api/types/loginSessionInfo"
time="2020-03-02T23:41:21Z" level=info msg="Authentication response code:200"
time="2020-03-02T23:41:21Z" level=info msg="Authentication successful"
time="2020-03-02T23:41:21Z" level=error msg="Cannot read directory: /sys/class/fc_host Error: open /sys/class/fc_host: no such file or directory"
time="2020-03-02T23:41:22Z" level=info msg="Executing NodeGetInfo. Host name:node05"

The last two lines repeats many times.

So, it looks like it may be something to do with the lack of fibre channel adapter on my worker nodes, but as I'm using the virtual storage appliance I should not need (and can not configure) FC adapters.

Is this currently a limitation of the CSI drivers? Is there a way round this? I'd appreciate any help / guidance anyone can give.

 

Many thanks

Carl

 

No Responses!
No Events found!

Top