Skip to main content
NetApp Knowledge Base

Restoring Trident Protect CRDs and AMRs after upgrade and cleanup job

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

Applies to

  • NetApp FAS8300
  • NetApp ONTAP 9.15.1P17 (Cluster-Mode)
  • NetApp Trident Protect 26.02.1
  • Kubernetes (OpenShift 4.20.21)

Issue

  • After upgrading Trident Protect on the destination cluster from version 25.0.2 to 26.02.1, all Trident Protect Custom Resource Definitions (CRDs) disappeared unexpectedly.
  • The Trident Protect deployment was stuck in an uninstalling/error state, with Application Mirror Relationships (AMRs) missing and only Trident Mirror Relationships (TMRs) and Persistent Volume Claims (PVCs) remaining.
  • Replication to the disaster recovery (DR) site stopped, causing concern about growing SnapMirror snapshots and potential risk of VMs going offline due to disk space exhaustion.
  • Observed error and log output:
#helm -n trident-protect ls
NAME NAMESPACE REVISION UPDATED STATUS CHART APPVERSION
trident-protect trident-protect 8 2026-05-24 06:03:22 uninstalling trident-protect-100.2602.1 26.02.1
#kubectl get crds | grep -i protect || echo NOTFOUND
NOTFOUND
#kubectl -n trident-protect get pods
NAME READY STATUS RESTARTS AGE
trident-protect-controller-manager-8d778848-9zhkj 1/1 Running 2 12d
trident-protect-cr-cleanup-pre-delete-4chtd0 1/1 Completed 0 7h27m
trident-protect-cr-cleanup-pre-delete-gmqhb0 1/1 Error 0 12h

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.