Trident NFS Volume Mount Fails with MountVolume SetUp failed for volume exit status 32 due to Delayed Export Policy Reconciliation
Applies to
- Astra Trident 25.10 (Kubernetes CSI driver)
- ONTAP NAS Economy backend with autoExportPolicy enabled
- Kubernetes environments using NFS Persistent Volumes
Issue
- When creating a Kubernetes pod that requires an NFS volume provisioned by Astra Trident, the pod remains stuck in the “
ContainerCreating” state. The following error is observed in the pod events and Trident logs:
MountVolume.SetUp failed for volume "pvc-xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx":rpc error: code = Internal desc = error mounting NFS volume 10.x.x.x:/trident_qtree_pool_<...>/<...> on mountpoint /var/lib/kubelet/pods/<...>/volumes/kubernetes.io~csi/<...>/mount: exit status 32- From the Trident node plugin logs:
mount.nfs4: access denied by server while mounting 10.x.x.x:/trident_qtree_pool_<...>/<...>- The issue was first observed after enabling Trident’s automatic export policy management (
autoExportPolicy: true) and specifyingautoExportCIDRs.
