Skip to main content
NetApp Knowledge Base

TRID-20198: Trident removes NFS export policy rules when the controller restarts with autoExportPolicy enabled

  1. Last updated
  2. Save as PDF
Views:
Visibility:
Public
Votes:
0
Category:
trident-kubernetes
Specialty:
snapx
Last Updated:

Issue

  • After upgrading Trident to 26.02.x, or after any restart of the Trident controller when an ontap-nas backend is configured with autoExportPolicy: true, the IP addresses of the nodes that already have volume publications are removed from the per-volume ONTAP NFS export policy causing mounts to fail.
  • New pods scheduled on the affected nodes cannot mount RWX NFS volumes and stay in ContainerCreating. The kubelet reports: mount.nfs: access denied by server while mounting <data_lif>:/<volume_name>

  • Pods that are already running keep their mount until they are restarted or rescheduled. The affected nodes do not recover on their own.

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.