Recurring “Update vSAN Configuration” Events in vCenter After vSAN Decommission

Products

• VMware vSAN

Issue/Introduction

Symptoms

After removing the vSAN configuration from the environment and migrating workloads to new storage, vCenter Server continues to display recurring “Update vSAN Configuration” tasks or events.

• vSAN is disabled at the cluster level.
• No vSAN disk groups are configured on any ESXi hosts.

[root@ESXi:~ ] esxcli vsan cluster get

vSAN Clustering is not enabled on this host.

[root@ESXi:~ ] vdq -iH
[root@ESXi:~ ]

• Despite this, vSAN-related events persist in vCenter tasks.

• vCenter Service Status: All core services, including vmware-vsan-health, are running:

root@vCenter[ /var/log/vmware/vsan-health ] # service-control -- status -- all
Running:
applmgmt lookupsve lwsmd observability observability-vapi pschealth vc-wsla-broker vlcm vmafdd vmcad vmdird vmware-analytics vmware-certificateauthority vmware-certificatemanagement vmware-cis-1
icense vmware-content-library vmware-eam vmware-envoy vmware-envoy-hgw vmware-envoy-sidecar vmware-hvc vmware-infraprofile vmware-perfcharts vmware-pod vmware-postgres-archiver vmware-rhttpproxy
vmware-sca vmware-sps vmware-stsd vmware-topologysvc vmware-trustmanagement vmware-updatemgr vmware-vapi-endpoint vmware-vdtc vmware-vmon vmware-vpostgres vmware-vpxd vmware-vpxd-svcs vmware-vsan
-health vmware-vsm vsphere-ui vstats vtsdb wcp
Stopped:
vmcam vmonapi vmware-imagebuilder vmware-netdumper vmware-rbd-watchdog vmware-vcha

Environment

VMware vSAN 8.x

Cause

This issue occurs when vSAN was disabled but not completely decommissioned.
Residual metadata and configuration records remain within the vCenter Server database, prompting vCenter to repeatedly attempt synchronization or remediation tasks against the ESXi hosts.

As a result, vCenter generates “Update vSAN Configuration” events even though vSAN is no longer active in the cluster.

Evidence - 

From the /var/log/vmware/vsan-health/vmware-vsan-health-service.log, it was observed that vCenter continued to identify cluster inconsistency and attempted to validate or repair host configurations:

YYYY-MM-DDTHH:MM:SS.000+00:00 INFO vaan-mgmt [07866] [VsanClusterPrototypeImpl: : RetrieveHostsInfos opID=vsan-PC-#############-##-#####] The cluster uuid in host host-### is , in ve is ######-####-####-####-############
YYYY-MM-DDTHH:MM:SS.000+00:00 INFO vaan-mgmt [07866] [VsanClusterPrototypeImpl: : RetrieveHostsInfos opID=vsan-PC-#############-##-#####] The cluster uuid in host host-### is , in ve is ######-####-####-####-############

These logs confirm that vCenter was still attempting to reconcile vSAN cluster membership information with hosts, even though vSAN clustering was disabled.

Resolution

Restart the vSAN Health Service on the vCenter Server to clear stale vSAN configuration tasks and refresh the vCenter database state.

Step - 

service-control -- status vmware-vsan-health

service-control -- stop vmware-vsan-health

service-control -- start vmware-vsan-health

Restarting the vmware-vsan-health service forces vCenter to clear residual task entries associated with old vSAN metadata.
This procedure is safe and does not impact other running vCenter services.

Additional Information

• Ensure all vSAN disk groups and datastore configurations are fully removed before disabling vSAN at the cluster level.
• vSANの廃止後に vCenter で 「vSAN構成の更新」 のイベントが繰り返し発生する