single vserver shown as"unhealthy" with empty "failed-reason"

• Config-replication warning
• Vserver shown as unhealthy
• Ability to switchover MetroCluster degraded

Example:

Cluster1::> metrocluster check show

Last Checked On: 10/19/2024 12:27:00

Component           Result
------------------- ---------
nodes               ok
lifs                ok
config-replication  warning
aggregates          ok
clusters            ok
connections         ok
volumes             ok
7 entries were displayed.

Cluster1::*> metrocluster vserver show  -fields failed-reason,failed-row,configuration-state  -configuration-state !healthy,!pending-switchback
cluster  vserver  configuration-state failed-row failed-reason
-------- -------- ------------------- ---------- -------------
Cluster1 vserver1 unhealthy           -          -

Cluster1::> metrocluster operation show
       Operation: switchover-simulate
           State: failed
      Start Time: 10/19/2024 12:23:46
        End Time: 10/19/2024 12:43:58
          Errors: Failed to validate the node and cluster components before the switchover operation.
                  Cluster1 (non-overridable veto): The operation timed out while waiting for Vserver configuration synchronization to complete. Vserver resynchronization is continuing in the background. Run "metrocluster vserver show -cluster fashak09" on both clusters, wait until the "Configuration State" of all Vservers is "healthy", and then retry the operation. Contact technical support for assistance if any Vserver remains unhealthy as indicated by a "Configuration State" shown as "degraded" or "unhealthy".

Cluster1::> 

• Manual run of metrocluster vserver resync does not fix the issue