Skip to main content
NetApp Knowledge Base

After defining new lifs in an ontap SVM and removing the old ones, old pods do not properly run and having mount issues

Views:
14
Visibility:
Public
Votes:
0
Category:
trident-openshift
Specialty:
SNAPX
Last Updated:

Applies to

  • Astra Trident 24.06
  • NetApp ONTAP 9.X
  • NFS protocol
  • RedHat OCP (OpenShift Container Platform)
  • Data lifs were not defined in the Trident backend configuration, so they are detected automatically by Trident

Issue

  • Defined new IP addresses for lifs in an ontap SVM
  • Old IP addresses were removed from the ontap SVM
  • New pods can properly mount PVCs using the new lifs
  • Pods created before the changes, can't access the new lifs defined in the SVM and having mount issues with the following error:

    Unable to attach or mount volumes: unmounted volumes=[<nameofPVC>], unattached volumes=[], failed to process volumes=[]: timed out waiting for the condition

 

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.