Skip to main content
NetApp Knowledge Base

Kubernetes NFS PVC Mount Fails with “access denied by server” – ONTAP SVM Root Volume Export Policy Missing Client Rule

  1. Last updated
  2. Save as PDF
Views:
62
Visibility:
Public
Votes:
0
Category:
trident-openshift
Specialty:
SNAPX
Last Updated:

Applies to

  • Trident CSI Driver
  • Kubernetes / OpenShift clusters
  • NFS-backed Persistent Volume Claims (PVCs)

Issue

Pods fail to mount NFS-backed PVCs, remaining stuck in the ‘ContainerCreating’ state.
Kubernetes events and Trident logs show repeated mount failures:

Pod Events:

Warning  FailedMount  kubelet  MountVolume.SetUp failed for volume "pvc-xxxx": rpc error: code=Internal desc=error mounting NFS volume <DataLIF IP>:/pvc_xxxx on mount point ...: exit status 32
Warning  FailedMount  kubelet  Unable to attach or mount volumes: unmounted volumes=[volume], unattached volumes=[], failed to process volumes=[]: timed out waiting for the condition

Trident CSI Logs:

mount.nfs: access denied by server while mounting <DataLIF IP>:/pvc_xxxx

Multiple volume attachments referencing the same PV were observed, but the PVC export policy was correct.

 

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.