Skip to main content
NetApp Knowledge Base

AppMirrorUpdate objects accumulate on destination cluster in Trident Protect

  1. Last updated
  2. Save as PDF
Views:
Visibility:
Public
Votes:
0
Category:
not set
Specialty:
not set
Last Updated:

Applies to

  • Trident Protect TP-26.02
  • AppMirrorRelationship (AMR)
  • AppMirrorUpdate (AMU) 

Issue

  • After performing AppMirrorRelationship operations with Trident Protect, AppMirrorUpdate  objects accumulate continuously in Kubernetes namespaces on the destination cluster.
  • The accumulation grows over time and does not resolve on its own.

Cause

  • The cleanupAMUs() function in the AppMirrorRelationship controller reads the list of AMU objects to delete from the informer cache. When a status conflict occurs during a reconcile pass, the reconcile restarts. Because the informer cache may not have processed earlier deletion events by the time the new reconciliation pass begins, cleanupAMUs() attempts to delete AMU objects that were already deleted in the prior pass
  • These deletion attempts return an Not Found error, which causes the reconciliation to fail again, triggering further retries and perpetuating the cycle.
  • New AMU objects continue to accumulate as a result.

Solution

  • Use a Kubernetes CronJob to periodically delete stale AMU objects from the affected namespaces.
  • A permanent fix is planned for a future Trident Protect release. The fix adds a Not Found guard in cleanupAMUs() to skip already-deleted AMU objects and stop the reconcile loop.

Partner Notes

partnerNotes_text

Additional Information

additionalInformation_text

Internal Notes

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.