Reoccurring failed metrocluster resync's due to Reason: Apply failed for Object
Applies to
- ONTAP 9
- Metrocluster
Issue
- Metrocluster resync continuously fails with the error below:
Reason: Apply failed for Object: volume Method: baseline. Reason: Internal Error. Reason entry doesn't exist
metrocluster vserver show
shows the following error:
Cluster : cluster1
Vserver : vserver1
Partner Vserver : vserver1-mc
Configuration State : degraded
Stream Status : operation-failed
Corrective Action : Resynchronize the configuration using "metrocluster vserver resync" command. Contact technical support for assistance if configuration-state does not change to healthy.
Failed Row : Table Name: volume, Operation: get, Fields: vserver1-mc volume1........
Failed Reason : Apply failed for Object: volume Method: baseline. Reason: [Job 1234] Job failed: entry doesn't exist
- On the source cluster, the volume listed in the above output is in the recovery queue
cluster2::*> volume recovery-queue show
Vserver Volume Deletion Request Time Retention Hours
--------- ----------- ------------------------ ---------------
vserver1
volume1
Mon Apr 29 07:42:13 2024 12