Fix NFS behavior

The current mount parameters are dangerous because the
system can mount a local storage instead of NFS at VM startup. New
params here avoid that. A software error is returned instead to anyone +
lazy loading of the folder.

Issue-ID: CLAMP-174
Change-Id: Ie68827ac94046a611b54e3bf5afaed18bc12bc78
Signed-off-by: Determe, Sebastien (sd378r) <sebastien.determe@intl.att.com>

diff --git a/deployment/heat/onap-oom/k8s_vm_entrypoint.sh b/deployment/heat/onap-oom/k8s_vm_entrypoint.sh
index 52f1204..4385295 100644 (file)
--- a/deployment/heat/onap-oom/k8s_vm_entrypoint.sh
+++ b/deployment/heat/onap-oom/k8s_vm_entrypoint.sh
@@ -34,7 +34,7 @@ EOF
 fi
 
 mkdir -p /dockerdata-nfs
-echo "__rancher_private_ip_addr__:/dockerdata-nfs /dockerdata-nfs nfs auto,nofail,noatime,nolock,intr,tcp,actimeo=1800 0 0" | tee -a /etc/fstab
+echo "__rancher_private_ip_addr__:/dockerdata-nfs /dockerdata-nfs nfs noauto,noatime,fg,retry=1,x-systemd.automount,_netdev,soft,nolock,intr,tcp,actimeo=1800 0 0" | tee -a /etc/fstab
 
 # Fix virtual memory allocation for onap-log:elasticsearch:
 echo "vm.max_map_count=262144" >> /etc/sysctl.conf