A NetApp running 9.0 has a svm publishing an NFS share (v3 v4 v4.1 enabled),
On an automation CI job we mount the nfs share on a VM running ontop of a physical server,
both VM and server are RHEL based, for the most part automation and share mounting works fine.
However if we run multiple automation jobs simultaneously,
only one job manages to mount the share on the VM, other job(s) fail to mount the NFS share.
The root cause of this happen as VMs use the same name (controller-2), they may simultaneously run on other servers/IPs,
thus netapp get's annoyed and reports this understandable error:
See The Solution
Check out the following documentation: https://docs.microsoft.com/en-us/azure/azure-netapp-files/configure-nfs-clients#configure-two-vms-with-the-same-hostname-to-access-nfsv41-volumes
It is Azure NetApp Files documentation, but the same solution applies. It is a client side unique identifier that needs to be set.
View solution in original post
You rock SeanLuce!
Didn't test it out (yet), sounds like it's another possible solution.
However I suspect setting unique IP per each automation job/share mount may be easier to implement, than having to automate generation of nfs4_unique_id per VM .
Anyway thank you very much for the tip!
This is also covered in this TR:
https://www.netapp.com/pdf.html?item=/media/10720-tr-4067.pdf page 124
Join our Discord Community