Skip to main content
NetApp Knowledge Base

Trident slow Volume Attachment after Data Center Failover

  1. Last updated
  2. Save as PDF
Views:
54
Visibility:
Public
Votes:
0
Category:
astra_trident
Specialty:
SNAPX
Last Updated:

Applies to

  • ONTAP 9
  • OpenShift Virtualization 4.18.36
  • Trident 25.10

Issue

Volumes created through Trident in the OpenShift environment on NetApp ONTAP  are no longer automatically assigned the expected snapshot policy. New Persistent Volume Claims (PVCs) result in NetApp volumes that either have no snapshot policy assigned or have an unexpected default applied.

 

  

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.