vSAN health alarm 'vSAN build recommendation engine' occurs
Article ID: 419116
Updated On:
Products
Issue/Introduction
vSAN health alarm 'vSAN build recommendation engine' occurs
・ "Unexpected VMware Update Manager (VUM) baseline creation failure. Please check vSAN and VUM logs for details" is displayed.
・vmware-vsan-health-service.log
-> An error occurred when creating a baseline on the Update Manager side from vsan-health service.
2025-10-27T05:04:00.494Z INFO vsan-mgmt[2823383] [VsanVumConnection::CreateBaselineFromOfficialPatches opID=noOpId] Creating baseline from ESX official patches VMware ESXi 8.0.3 Patch Release - ESXi80U3e-24674464 with vSAN recommended patches ESXi80U3g-24859861 ...
2025-10-27T05:04:00.495Z INFO vsan-mgmt[2823383] [VsanVumConnection::_LookupPatchBaseline opID=noOpId] Looking up baseline for patch VMware ESXi 8.0.3 Patch Release - ESXi80U3e-24674464 with vSAN recommended patches ESXi80U3g-24859861 (keys: [], hash: None)...
2025-10-27T05:04:00.495Z INFO vsan-mgmt[2823383] [VsanVumCoreUtil::QueryBaselinesForUpdatefun opID=noOpId] Query baseline for update []
2025-10-27T05:04:00.495Z INFO vsan-mgmt[2823383] [VsanVumCoreUtil::retryWrapper opID=noOpId] failed with VUM exception Required field "update" not provided (not @optional)
2025-10-27T05:04:00.495Z INFO vsan-mgmt[2823383] [VsanVumCoreUtil::CreateBaselineFun opID=noOpId] creating Baselines with spec (integrity.UpdateBaselineSpec) {
2025-10-27T05:04:00.507Z INFO vsan-mgmt[2823383] [VsanVumCoreUtil::retryWrapper opID=noOpId] failed with VUM exception (vim.fault.AlreadyExists) {
msg = "The specified key, name, or identifier 'VMware ESXi 8.0.3 Patch Release - ESXi80U3e-24674464 with vSAN recommended patches ESXi80U3g-24859861' already exists.",
name = 'VMware ESXi 8.0.3 Patch Release - ESXi80U3e-24674464 with vSAN recommended patches ESXi80U3g-24859861'
}
2025-10-27T05:04:00.519Z ERROR vsan-mgmt[2823383] [VsanVumConnection::RemediateAllClusters opID=noOpId] Failed to remediate cluster 'vim.ClusterComputeResource:domain-c9'
Traceback (most recent call last):
File "bora/vsan/vum/vpxd/pyMoVsan/VsanVumConnection.py", line 1304, in RemediateAllClusters
File "bora/vsan/vum/vpxd/pyMoVsan/VsanVumConnection.py", line 829, in RemediateVsanClusterInVum
File "bora/vsan/vum/vpxd/pyMoVsan/VsanVumConnection.py", line 448, in CreateClusterBaselineGroup
File "bora/vsan/MgmtServer/VsanMgmtSvcMain.py", line 167, in _PatchedDataObjectInit
File "bora/vsan/MgmtServer/VsanMgmtSvcMain.py", line 160, in _DataObjectSlowInit
TypeError: For field 'baseline' expected type int, but got NoneType
・vmware-vum-server.log
-> The error occurs because the baseline for the patch requested by the vsan-health service already exists.
2025-10-27T05:04:00.503Z info vmware-vum-server[152899] [Originator@6876 sub=Activation] [activationValidator 369] Leave Validate. Succeeded for integrity.BaselineManager.create on target: Integrity.BaselineMgr^M
[#108] 2025-10-27T05:04:00.505Z error vmware-vum-server[152899] [Originator@6876 sub=BaselineMgr] [baselineMgr 1621] Vcidb ERROR: Element with same name already exists - VMware ESXi 8.0.3 Patch Release - ESXi80U3e-24674464 with vSAN recommended patches ESXi80U3g-24859861 ^M
[#108] --> ^M
[#108] --> Exiting....^M
[#108] --> ^M
[#108] 2025-10-27T05:04:00.506Z error vmware-vum-server[152899] [Originator@6876 sub=BaselineMgr] [baselineMgr 1621] [backtrace begin] product: VMware Update Manager, version: 8.0.2, build: build-23929136, tag: vmware-vum-server, cpu: x86_64, os: linux, buildType: release^M
[#108] --> backtrace[00] libvmacore.so[0x0053D3AB]^M
[#108] --> backtrace[01] libvmacore.so[0x0043197E]: Vmacore::System::Stacktrace::CaptureFullWork(unsigned int)^M
[#108] --> backtrace[02] libvmacore.so[0x00444252]: Vmacore::System::SystemFactory::CreateBacktrace(Vmacore::Ref<Vmacore::System::Backtrace>&)^M
[#108] --> backtrace[03] libvci-vcIntegrity.so[0x007464F0]: Integrity::BaselineMgrImpl::Create(Integrity::BaselineSpec*, bool, Integrity::BaselineInfo::ContentType)^M
[#108] --> backtrace[04] libintegrity-types.so[0x0020FB46]^M
[#108] --> backtrace[05] libvmomi.so[0x001BE4DE]: Vmomi::AdapterServer::ExecuteActivation(Vmomi::Activation*, bool)^M
[#108] --> backtrace[06] libvmomi.so[0x001BF3C3]^M
[#108] --> backtrace[07] libvmomi.so[0x001BC3D5]: Vmomi::AdapterServer::ExecuteStep(Vmomi::Activation*, bool)^M
[#108] --> backtrace[08] libvmomi.so[0x001BC8F0]^M
[#108] --> backtrace[09] libvmomi.so[0x001BE2F4]^M
[#108] --> backtrace[10] libvmomi.so[0x001BE37A]^M
[#108] --> backtrace[11] libvmacore.so[0x0037DBE6]^M
[#108] --> backtrace[12] libvmacore.so[0x003834F9]^M
[#108] --> backtrace[13] libvmacore.so[0x0051D093]^M
[#108] --> backtrace[14] libpthread.so.0[0x00008EAE]^M
[#108] --> backtrace[15] libc.so.6[0x000FDE2F]^M
[#108] --> backtrace[16] (no module)^M
[#108] --> [backtrace end]^M
Environment
vCenter Server 8.0 U2
Cause
This is an issue in the vsan health service that causes it to create baselines with the same name multiple times.
Resolution
The fix is in vCenter Server 8.0 U3 and greater.
There is currently no workaround for vCenter Server 8.0 U2.
Feedback
