1 Rookie

 • 

13 Posts

5772

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 

42 Posts

April 15th, 2021 23:00

Hi @LudovitScholtz 

We would like to have a zoom session live to have an understanding on your environment. 

This would help us to give a better solution also. 

Kindly let us know the time and provide us your email to connect with you.

Regards

Thar_J

 

10 Posts

April 22nd, 2021 04:00

It looks like I am experiencing an identical problem. I'm trying to configure OpenShift 4 to work with a Dell Unity which is available via iSCSI and NFS. The node daemonset always crashes with

 

 

time="2021-04-21T08:39:09Z" level=error arrayid=ckm00201700161 runid=node-2231 msg="Cannot read directory: /sys/class/fc_host Error: open /sys/class/fc_host: no such file or directory" func="github.com/dell/csi-unity/service/utils.GetFCInitiators()" file="/go/src/csi-unity/service/utils/emcutils.go:90"

 

 

1 Rookie

 • 

13 Posts

April 22nd, 2021 07:00

We have attempted once again..

Still no luck here.. https://apps.scholtz.sk/unity15-20210422.zip (

I have created full installation script from scratch (we used namespace csi15 now for driver) Also you can find in the zip the logs and some screenshots)

./install15.sh

I assume there might be two potential errors:

1) documentation says: to use NFS protocol, NFS utility packages needs to be installed

We assume that it is installed on ubuntu by "sudo apt install nfs-common"

 

We can meet on 23.4. at 14:00 CET or 28.4. at 14:00 CET or 29.4. at 14:00 CET for call if you want

2) perhaps there might be some error in myvalues.yaml file..

Somewhere in this section

storageArrayList:
- name: "VIRT2109YFHRLA"
isDefaultArray: "false"
storageClass:
storagePool: pool_2
FsType: "ext4"
thinProvisioned: "true"
isDataReductionEnabled: "false"
tieringPolicy: "0"
hostIOLimitName: ""
nasServer: "nas_1"
reclaimPolicy: Delete
snapshotClass:
retentionDuration: ""

Infra department is however very worried that even if we do the pure NFS installation, it creates initiator in the unity storage.. 

Storage procols defined in myvalues are

storageClassProtocols:
- protocol: "NFS"
# - protocol: "iSCSI"
# - protocol: "FS"

This means that there is still some serious bug within csi driver and uses iSCSI if it is explicitly set not to do that..

Note, that the kubectl get sc lists only nfs storage class.. If it works with iSCSI, there is something wrong.

42 Posts

April 23rd, 2021 00:00

Hi @LudovitScholtz 

Kindly provide your email address to connect.

 

 

1 Rookie

 • 

13 Posts

April 25th, 2021 04:00

Hi, it seems i dont have rights to update the subject.. or can you please navigate me where to do it?

Also note in regards of last logs, the main issue is somewhere in the csi-driver because it does not provision the volume.. Weird thing is that it does not go to any logs in the controller 

https://apps.scholtz.sk/pv-not-created2.png

42 Posts

April 29th, 2021 03:00

Hi @jgazeley

Would like to know which version of Dell unity Driver you are using.

Are you able to install the unity driver.

42 Posts

April 29th, 2021 04:00

Hi @jgazeley
Kindly share the controller and node logs of unity driver for further investigations.

10 Posts

April 30th, 2021 01:00

Hi @Thar_J,

I opened a new thread for my own problem so it's probably best to follow up there  https://www.dell.com/community/Containers/csi-unity-crashloop-due-to-quot-fc-host-no-such-file-or/m-p/7863527#M1572

Thanks

No Events found!

Top