vSAN 7.x
vSAN 8.x
The issue occurs when multiple vSAN Witness Appliances are deployed with identical UUIDs. This typically results from cloning an existing Witness VM or deploying multiple appliances using the same OVA/OVF image without ensuring a unique UUID is generated for each instance.
It is important to observe that these symptoms may arise during cluster refresh operations, particularly when the system accesses the witness appliance after a partition has occurred.
Re-deploy the Witness Appliance from the official OVA. Refer : Deploying a vSAN Witness Appliance & Download location of vSAN Witness Appliance and File Service Appliance
Note :
Avoid cloning existing appliances, as this can lead to duplicate UUIDs, which may cause multiple stretched clusters to unintentionally share the same witness.
If you're using a common image across environments (e.g., in a Private Cloud setup), ensure that each cluster has a separately deployed Witness Appliance to maintain unique UUIDs.