13 Posts
0
1486
csi-unity : volumes created on storage, but no access defined
Hi,
I'm trying to integrate the unity CSI driver on Kubernetes.
Context :
- Kubernetes 1.20 on CentOS 7 or Kubernetes 1.19 on Ubuntu 20.04 (same troubles)
- All nodes are VMware VMs
- The storage is an UnityVSA
- CSI Driver version 1.5
- iSCSI and NFS configuration
- the two Kubernetes clusters are set-up in 'External Cloud Provider' mode, as they are also configured to use the VSphere CPI and CSI
- The whole environment is in a Rancher context, but I don't think it's pretty relevant in this case
After some diggings, I was able to install the driver. At this point, the driver installation goes without errors (I had to add a little wait time in the waitOnRunning function in csi-install.sh script, without that wait time, the script didn't detect the end of the "Deployment unity-controller")
After this installation, everythings seems to be OK. I can see that the iSCSI part is well done between the Kubernetes nodes and the storage.
Now I run the test/sample.yaml (a slightly edited version to remove any reference to the FC vol, pvol0), and the two volumes are created on the UnityVSA :
- One block volume size 12 GiB
- One FileSystem size 11,5 GiB, affected to the correct nas server.
But still, in the host part, the new Block disk isn't associated with any hosts, and I don't see any NFS share associated with the new filesystem of my NAS Server.
I don't know exactly how to find out the missing part in my configuration.
However, I enconter this message (as a 'related event') of the pod created by sample.yaml :
| FailedMount (10) | 56 secs ago | Unable to attach or mount volumes: unmounted volumes=[pvol1 pvol2], unattached volumes=[pvol1 pvol2 unitytest-token-q7m8j]: timed out waiting for the condition |
| FailedMount (2) | 3.1 mins ago | Unable to attach or mount volumes: unmounted volumes=[pvol2 pvol1], unattached volumes=[pvol2 unitytest-token-q7m8j pvol1]: timed out waiting for the condition |
| FailedAttachVolume (23) | 4 mins ago | AttachVolume.Attach failed for volume "csivol-b9ab7e02c5" : rpc error: code = InvalidArgument desc = Unity client not found for array 01 |
| FailedMount (3) | 5 mins ago | Unable to attach or mount volumes: unmounted volumes=[pvol1 pvol2], unattached volumes=[unitytest-token-q7m8j pvol1 pvol2]: timed out waiting for the condition |
| FailedAttachVolume (21) | 8 mins ago | AttachVolume.Attach failed for volume "csivol-083bb2f9cc" : rpc error: code = InvalidArgument desc = Unity client not found for array 01 |
I was "googleling" a lot, but didn't find anything relevant.
Any hints ?
Thanks,
Pascal
Schirrms
13 Posts
1
May 20th, 2021 09:00
......
Sure Enough, renaming the Unity VAS from 'unityvsa-d-01' to 'UNITYVSAD01' did the trick.
Hi EMC Guys, did you know that renaming a storage is a valid operation ?
Thanks anyway,
Pascal
Schirrms
13 Posts
0
May 20th, 2021 08:00
Hi,
That would be 'too silly' but :
The name of my storage has been changed : it's 'unityvsa-d-01'
Could that be the reason of some troubles ? As I see that the '-' (minus sign) is used as a field separatoir in the VolumeHandle.
please, tell my I'm wrong...
Thanks,
Pascal
ankur.patel
286 Posts
0
May 20th, 2021 11:00
Did you change the name of the unity AFTER installing the CSI driver?
Schirrms
13 Posts
1
May 21st, 2021 00:00
Hi Ankur,
Na, I did remove all CSI configuration before I renamed the Unity VSA. But, to be honest, the whole thing is not totally clean.
It seems to be OK on the vsa side (with some manual cleanup on the storage before I rename an reintegrate), but it's not so clean on the k8s side.
Anyway, I'll have to reinstall a complete cluster to (fanally) produce an usable documentation (not to critic the Dell/Emc doc, but that's not exactly what we use internally, I need a more straigthforward documentation).
One good thing is that, with that (wonderful) vsa tool, I didn't have to play with our 'real' Unity 480
One badest thing is that our 'production Unity' are also renamed, with '-' in the name (as this is our standard way of naming system, and as this was until yesterday a legit action on Unity !)
Pascal