Promoting a tridentSnapMirror caused Vserver temporarily locked from changes

Last updated
Save as PDF
Share
1. Share
2. Tweet
3. Share

Views:: 40

Visibility:: Public

Votes:: 0

Category:: trident-kubernetes

Specialty:: snapx

Last Updated:

Applies to

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

Issue

With a Trident Protect mirror setup, promoting the mirror initially has no issue. However when trying to revert again (promoting in the opposite direction), it fails with an ONTAP vserver locking error.

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"

On the ONTAP side, this error comes from attempting to add new exports for the Kubernetes/Openshift cluster receiving the promotion.

This error is also seen on a lot of other export policy changes from the mlog/audit.log in either adding ro removing rules with REST API calls:

DELETE /api/protocols/nfs/export-policies/<POLICY-ID>/rules/<RULE-NUMBER>
POST /api/protocols/nfs/export-policies/<POLICY-ID>/rules : {"clients":[{"match":"<IP-ADDRESS>"}],"ro_rule":["any"],"rw_rule":["any"],"superuser":["any"],"protocols":["nfs"]}