Skip to main content
NetApp Knowledge Base

AppMirrorRelationship (AMR) Stuck Waiting for Destination PVCs to be Bound

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

Applies to

  • Trident Protect (TP)
  • AppMirrorRelationship (AMR)

Issue

  • When deploying an AppMirrorRelationship (AMR) with TP the destination PVCs remain in the Pending state and are not bound. T
  • The AMR status is stuck, and data replication does not proceed.
  • All destination PVCs in the mirror namespace stay in Pending state.
  • Message seen:

Message: Waiting for destination PVC 'test-topology-application-mirror-ns/test-volume-test-app-1' to be 'Bound'
Reason: Waiting
Status: False
Type: DestinationPVCsBound

 

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.