Destination SVM stuck in unhealthy state after source deletion

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

Views:: 178

Visibility:: Public

Votes:: 0

Category:: metrocluster

Specialty:: metrocluster

Last Updated:

Applies to

MetroCluster
SVM source deletion
Destination SVM (-mc)
DR Config Replication alert

Issue

After source SVM was deleted the destination vserver on the DR cluster is reported in unhealthy state:

::> metrocluster vserver show  
                              Cluster  : ClusterA
                              Vserver  : SVM_A
                      Partner Vserver  : SVM_A-mc
                  Configuration State  : unhealthy

job show -id <job-id> -instance show displays a vserver deletion job as failed with Reason: Apply failed for object rest_roles_ui:

                      Job ID: 378900
              Owning Vserver: SVM_A
                        Name: Vserver Delete
                 Description: Delete SVM_A-mc
                    Priority: High
                        Node: NodeA_1
                    Affinity: Cluster
                    Schedule: @now
                  Queue Time: 12/09 14:22:48
                  Start Time: 12/09 14:22:52
                    End Time: 12/09 14:22:55
              Drop-dead Time: -
                  Restarted?: false
                       State: Failure
                 Status Code: 1
           Completion String: 
Reason: Apply failed for object rest_roles_ui