Skip to main content
NetApp Knowledge Base

Promoting a tridentSnapMirror caused Vserver temporarily locked from changes

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

Applies to

  • Trident for Kubernets and Openshift
  • ONTAP 9.16.1P11
  • MCC, SVM-DR

Issue

The full error seen in the Trident events from trident-controller was:
time="2026-05-26T07:47:11Z" level=error msg="Could not promote mirror" TridentMirrorRelationship=<TMR_NAME> crdControllerEvent=update error="API State: failure, Message: This Vserver is temporarily locked from changes while recording the configuration baseline. Try again in a few minutes or manually stop configuration replication by running \"vserver config-replication pause\" and retry the command., Code: 2621573"
logLayer=crd_frontend logSource=trident-crd-controller requestID=<REQUEST_UID> requestSource=CRD workflow="cr=reconcile"

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.