Start a Conversation

Solved!

Go to Solution

1 Rookie

 • 

13 Posts

5733

March 6th, 2021 11:00

csi-unity does not work

Hi,

we were trying to do pure NFS share with Unity in Kubernetes 19 using csi-unity using 3 master and 3 worker nodes on bare metal.

We have installed Dell EMC UnityVSA  for testing purposes before we wanted to do it in production.

We have watched videos and study this community closely but we were unable to solve the issue.

We believe there are 2 major bugs:

1) NFS is not supported without other driver
2) iSCSI driver cannot run on multiple worker nodes

Ad 1)
This person was hit with the same issue: https://www.dell.com/community/Containers/csi-unity-nfs-claim-pending/m-p/7813344 Known bugs: "For NFS volume and pod creation to succeed there must be minimum one worker node with iSCSI support and with a successful iSCSI login in to the array"

We would like to see no attempts with FC or iSCSI communication in the daemon set or the controller. We do not understand why the FC or iSCSI must be present in the configuration because it is technologically absolutely something different.

Ad 2)
The first pod in the daemon set creates Initiator in unity, but the other pod from other node tries to create initiator with the same name and fails. We have found no configuration options in any of the files used with the installation or in the running pod. Also it does not create any initiator path.

 

Is there any estimate when the issue #1 will be solved?

Does anybody have any hint how to solve issue #2?

Thanks 

No Responses!
No Events found!

Top