......   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 
Hi, I'm trying to integrate the unity CSI driver on Kubernetes. Context : 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 :   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 :   I was "googleling" a lot, but didn't find anything relevant. Any hints ? Thanks, Pascal
csi-unity : volumes created on storage, but no access defined