<p>In our OpenShift 3.11 cluster, we are trying to use NFS through a PersistentVolume and a NFS volume previously created on a external NFS storage (a Isilon Storage).
We created and applied succesfully the PersistentVolume and the PersistentVolumeClaim on the Kubernetes/OpenShift Layer. The PVC binds the PV correctly, but when checking the Deployment events we face an error in the mounting NFS phase.</p>
<p>PersistentVolume:</p>
<pre><code>apiVersion: v1
kind: PersistentVolume
metadata:
  name: tool1pv
spec:
  capacity:
    storage: 100Gi 
  accessModes:
  - ReadWriteOnce 
  nfs: 
    path: /tool1shareenv1
    server: tommytheserver.companydomain.priv
  persistentVolumeReclaimPolicy: Retain
  claimRef:
    name: tool1claimenv1
    namespace: ocpnamespace1

</code></pre>
<p>PersistentVolumeClaim:</p>
<pre><code>apiVersion: v1
kind: PersistentVolumeClaim
metadata:
  name: tool1claimenv1
spec:
 accessModes:
   - ReadWriteOnce
 resources:
  requests:
    storage: 100Gi
 volumeName: tool1pvenv1 
</code></pre>
<p>When checking the Development Events, we see a &quot;No such file&quot;:</p>
<pre><code>MountVolume.SetUp failed for volume &quot;tool1pvenv1&quot; : mount failed:
 exit status 32 Mounting command: systemd-run Mounting arguments: --description=Kubernetes transient mount for /var/lib/origin/openshift.local.volumes/pods/f1cb1291-fe12-01ea-bb92-0050123aa39be/volumes/kubernetes.io~nfs/tool1pvenv1 --scope -- mount -t nfs tommytheserver.companydomain.priv:/tool1shareenv1
/var/lib/origin/openshift.local.volumes/pods/f1cb9191-fe73-11ea-bb92-005056ba12be/volumes/kubernetes.io~nfs/tool1pvenv1d Output: Running scope as unit run-74039.scope. **mount.nfs: mounting tommytheserver.companydomain.priv:/tool1env1 failed, reason given by server: No such file or directory**
</code></pre>
<p>We investigated the <code>server</code> and the <code>path</code> fields and tried different varations such as:</p>
<p>PersistentVolumeVersion2:</p>
<pre><code> apiVersion: v1
kind: PersistentVolume
metadata:
  name: tool1pv
spec:
  capacity:
    storage: 100Gi 
  accessModes:
  - ReadWriteOnce 
  nfs: 
    path: /tool1shareenv1
    server: tommytheserver.companydomain.priv/tool1shareenv1
  persistentVolumeReclaimPolicy: Retain
  claimRef:
    name: tool1claimenv1
    namespace: ocpnamespace1
</code></pre>
<p>but we're still faceing the same <code>No such file</code> error.</p>
<p>How can we troubleshoot it ?</p>

lsambo
<p>Normally to troubleshoot something like this I would...</p>
<ol>
<li>Double check that your share path actually exists</li>
<li>Get the IP address of your node where your pod ran and ssh onto it.  You can get the IP like this:</li>
</ol>
<pre><code>kubectl get pod &lt;podname&gt; -o wide -n namespace
</code></pre>
<p>Then I would make sure I can connect to the nfs server where the share exists:</p>
<pre><code>telnet &lt;nfs server&gt; port
</code></pre>
<ol start="3">
<li>Following that I would run <code>dmesg</code> to see mounting related errors</li>
<li>I would try to mount the volume myself using the same arguments your error is showing.  ie-</li>
</ol>
<pre><code>mount -t nfs tommytheserver.companydomain.priv:/tool1shareenv1
</code></pre>
<p>It is difficult to provide a specific answer without seeing the results of these troubleshooting steps.  But, that is the approach I would take.</p>
