vCenter Server is showing alarm "The name 'alarm.vsan.health.test.cloudhealth.xxx' already exists"

Products

• VMware vSAN

Issue/Introduction

Symptoms:

• In /var/log/vmware/vsan-health/vmware-vsan-health-service.log on vCenter Server you see errors similar to:

2019-10-16T13:21:51.283Z ERROR vsan-mgmt[CloudHealthQuery-139886885975808] [VsanCloudHealthDaemon::run opID=noOpId] Failed to update online resources, details: Cannot update cloudHealth extension or regisiter alarms, detail is: (vim.fault.DuplicateName) {
   msg = "The name 'alarm.vsan.health.test.cloudhealth.v1diskcheck' already exists.",
   faultCause = <unset>,
   faultMessage = (vmodl.LocalizableMessage) [],
   name = 'alarm.vsan.health.test.cloudhealth.v1diskcheck',
   object = 'vim.alarm.Alarm:alarm-1409'
}

Environment

VMware vSAN 6.x

Resolution

This is a known issue affecting 6.7 U3 and has been addressed in vCenter 7.0.

Workaround:
To workaround this issue, vSAN Health service on the vCenter Server can be restarted by running following command:
 

service-control --restart vsan-health

There is no impact on any vSAN cluster expected.

If the alarm comes back, try the following steps:
1. Go to vCenter -> Configure -> Alarm Definition
2. Find alarm "vSAN online health alarm 'Customer advisory for <alarm name mentioned after cloudhealth>'"
3. Delete this alarm.
4. Restart vSAN Health service as outlined above.

The deleted alarm will be added back. This is due to we have a mechanism to check and re-register all the system alarms when vSAN Health Service restarts.