Skip to main content
NetApp Knowledge Base

Configuration Mismatch Between Trident and Openshift after Ransomware policy change

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

Applies to

  • Trident integration with OpenShift Container Platform (OCP)
  • NFS protocol environments
  • Trident-controlled volumes

Issue

A Trident-controlled ONTAP volume had its configuration parameters (max-grow, snapshot policy, snapshot reserve) modified by mistake during anti-ransomware and secure snapshot implementation. This resulted in a mismatch between the ONTAP volume size and configuration and the OCP Persistent Volume Claim (PVC) quota.

Log Output / Symptom:

  • ONTAP volume: 225GB size, 146GB data written
  • OCP PVC quota: 50GB
  • Trident config snapshotReserve: 10%, snapshotPolicy: daily
  • Volume config: snapshotReserve was 20%, snapshotPolicy

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.