Unexpected VMware Update Manager (VUM) baseline creation failure.
Article ID: 326404
Updated On:
Products
VMware vSAN
Issue/Introduction
Resolving the warning "Unexpected VMware Update Manager (VUM) baseline creation failure. Please check vSAN and VUM logs for details" when vSAN health service on vCenter is unable to create default vSAN baseline.
Symptoms:
In vSAN Skyline Health, you will see following warnings:
Symptoms:
In vSAN Skyline Health, you will see following warnings:
- "Unexpected VMware Update Manager (VUM) baseline creation failure. Please check vSAN and VUM logs for details"
- "vSAN release catalog is up-to-date" and marked Green.
Environment
VMware vSAN 6.x
Cause
Following log pattern can be seen on the vCenter server in log file /var/log/vmware/vsan-health/vmware-vsan-health-service.log:
2020-01-14T14:05:07.503+06:00 INFO vsan-mgmt[Thread-974] [VsanVumConnection::_PrepareReleaseInfo opID=noOpId] build = {'release': {'baselineName': 'VMware ESXi 6.7.0 U3
(build 14320388)', 'partner': {'hpe': {'baselineName': 'HPE-Gen9plus Customized VMware ESXi 6.7.0 U3 (build 14320388)', 'downloadurl': 'https://download2.vmware.com/so
ftware/vi/67/VMware-ESXi-6.7.0-Update3-14320388-HPE-Gen9plus-670.U3.10.4.5.19-Aug2019.iso', 'message1': 'HPE Gen9 Plus Custom Image for ESXi 6.7 Update 3', 'params': '%
7B%22sourcefilesize%22%3A%22355.92+MB%22%2C%22dlgcode%22%3A%22OEM-ESXI67U2-HPE%22%2C%22languagecode%22%3A%22en%22%2C%22source%22%3A%22vswa%22%2C%22downloadtype%22%3A%22
manual%22%2C%22eula%22%3A%22Y%22%2C%22downloaduuid%22%3A%2217b15bf9-b98f-489e-8783-2e5f7bcf53a3%22%2C%22purchased%22%3A%22Y%22%2C%22dlgtype%22%3A%22Custom+ISO%22%2C%22p
roductversion%22%3A%226.7.0+U2%22%7D', 'profileName': 'HPE-ESXi-6.7.0-Update3-iso-Gen9plus-670.U3.10.4.5.19'}}, 'vcVersion': ['6.7.0 Update 3'], 'isoDisplayName': 'VMwa
re ESXi Release 6.7.0 U3, Build 14320388', 'profileName': 'ESXi-6.7.0-20190802001-standard', 'patchids': ['ESXi670-Update03'], 'patchDisplayName': 'VMware ESXi 6.7.0 U
3 (Patch ESXi670-Update03)', 'bldnum': 14320388}}
2020-01-14T14:05:07.504+06:00 INFO vsan-mgmt[Thread-974] [VsanVumConnection::_PrepareDriverInfo opID=noOpId] drivers = []
2020-01-14T14:05:07.504+06:00 INFO vsan-mgmt[Thread-974] [VsanSupportBundleHelper::parseSystemProxies opID=noOpId] VCSA proxy is disabled.
2020-01-14T14:05:08.366+06:00 INFO vsan-mgmt[Thread-974] [VsanVumConnection::_UploadBuildsAndDrivers opID=noOpId] Upload comlepeted!
2020-01-14T14:05:08.379+06:00 INFO vsan-mgmt[Thread-974] [VsanVumConnection::_LookupPatchBaseline opID=noOpId] Looking up baseline for patch VMware ESXi 6.7.0 U3 (Patch
ESXi670-Update03) with vSAN recommended patches ESXi670-201912001 (keys: [], hash: None)...
2020-01-14T14:05:08.379+06:00 INFO vsan-mgmt[Thread-974] [VsanVumCoreUtil::QueryBaselinesForUpdatefun opID=noOpId] Query baseline for update []
2020-01-14T14:05:08.380+06:00 INFO vsan-mgmt[Thread-974] [VsanVumCoreUtil::retryWrapper opID=noOpId] failed with VUM exception Required field "update" not provided (not
@optional)
2020-01-14T14:05:08.380+06:00 ERROR vsan-mgmt[Thread-974] [VsanVumConnection::RemediateAllClusters opID=noOpId] Failed to remediate cluster 'vim.ClusterComputeResource:
domain-c66'
Traceback (most recent call last):
File "/usr/lib/vmware-vpx/vsan-health/pyMoVsan/VsanVumCoreUtil.py", line 150, in retryWrapper
return f(self, *args)
File "/usr/lib/vmware-vpx/vsan-health/pyMoVsan/VsanVumCoreUtil.py", line 234, in QueryBaselinesForUpdatefun
result = bm.QueryBaselinesForUpdate(update = update)
File "/usr/lib/vmware/site-packages/pyVmomi/VmomiSupport.py", line 557, in <lambda>
self.f(*(self.args + (obj,) + args), **kwargs)
File "/usr/lib/vmware/site-packages/pyVmomi/VmomiSupport.py", line 362, in _InvokeMethod
list(map(CheckField, info.params, args))
File "/usr/lib/vmware/site-packages/pyVmomi/VmomiSupport.py", line 887, in CheckField
raise TypeError('Required field "%s" not provided (not @optional)' % info.name)
TypeError: Required field "update" not provided (not @optional)
Traceback (most recent call last):
File "/usr/lib/vmware-vpx/vsan-health/pyMoVsan/VsanVumConnection.py", line 1595, in RemediateAllClusters
self.RemediateVsanClusterInVum(vvchs, cluster)
File "/usr/lib/vmware-vpx/vsan-health/pyMoVsan/VsanVumConnection.py", line 1329, in RemediateVsanClusterInVum
patchNames, patchIds)
File "/usr/lib/vmware-vpx/vsan-health/pyMoVsan/VsanVumConnection.py", line 1184, in _CreatePatchBaselines
self.CreateBaselineFromOfficialPatches(patchName, patchIds)
File "/usr/lib/vmware-vpx/vsan-health/pyMoVsan/VsanVumConnection.py", line 416, in CreateBaselineFromOfficialPatches
baseline = self._LookupPatchBaseline(name, keys)
File "/usr/lib/vmware-vpx/vsan-health/pyMoVsan/VsanVumConnection.py", line 454, in _LookupPatchBaseline
result = self.QueryBaselinesForUpdate(update = updateKeys)
File "/usr/lib/vmware-vpx/vsan-health/pyMoVsan/VsanVumCoreUtil.py", line 237, in QueryBaselinesForUpdate
return self.retryWrapper(QueryBaselinesForUpdatefun, update)
File "/usr/lib/vmware-vpx/vsan-health/pyMoVsan/VsanVumCoreUtil.py", line 163, in retryWrapper
assert(False)
AssertionError
2020-01-14T14:05:08.381+06:00 INFO vsan-mgmt[Thread-974] [VsanVumSystemUtil::GetConfigIssueIds opID=noOpId] Get config issue id ['health.test.vum.createBaselineFailed'] for entity domain-c66
2020-01-14T14:05:08.382+06:00 INFO vsan-mgmt[Thread-974] [VsanVumSystemUtil::AddConfigIssue opID=noOpId] Skip create baseline failure when there is other issues
2020-01-14T14:05:07.503+06:00 INFO vsan-mgmt[Thread-974] [VsanVumConnection::_PrepareReleaseInfo opID=noOpId] build = {'release': {'baselineName': 'VMware ESXi 6.7.0 U3
(build 14320388)', 'partner': {'hpe': {'baselineName': 'HPE-Gen9plus Customized VMware ESXi 6.7.0 U3 (build 14320388)', 'downloadurl': 'https://download2.vmware.com/so
ftware/vi/67/VMware-ESXi-6.7.0-Update3-14320388-HPE-Gen9plus-670.U3.10.4.5.19-Aug2019.iso', 'message1': 'HPE Gen9 Plus Custom Image for ESXi 6.7 Update 3', 'params': '%
7B%22sourcefilesize%22%3A%22355.92+MB%22%2C%22dlgcode%22%3A%22OEM-ESXI67U2-HPE%22%2C%22languagecode%22%3A%22en%22%2C%22source%22%3A%22vswa%22%2C%22downloadtype%22%3A%22
manual%22%2C%22eula%22%3A%22Y%22%2C%22downloaduuid%22%3A%2217b15bf9-b98f-489e-8783-2e5f7bcf53a3%22%2C%22purchased%22%3A%22Y%22%2C%22dlgtype%22%3A%22Custom+ISO%22%2C%22p
roductversion%22%3A%226.7.0+U2%22%7D', 'profileName': 'HPE-ESXi-6.7.0-Update3-iso-Gen9plus-670.U3.10.4.5.19'}}, 'vcVersion': ['6.7.0 Update 3'], 'isoDisplayName': 'VMwa
re ESXi Release 6.7.0 U3, Build 14320388', 'profileName': 'ESXi-6.7.0-20190802001-standard', 'patchids': ['ESXi670-Update03'], 'patchDisplayName': 'VMware ESXi 6.7.0 U
3 (Patch ESXi670-Update03)', 'bldnum': 14320388}}
2020-01-14T14:05:07.504+06:00 INFO vsan-mgmt[Thread-974] [VsanVumConnection::_PrepareDriverInfo opID=noOpId] drivers = []
2020-01-14T14:05:07.504+06:00 INFO vsan-mgmt[Thread-974] [VsanSupportBundleHelper::parseSystemProxies opID=noOpId] VCSA proxy is disabled.
2020-01-14T14:05:08.366+06:00 INFO vsan-mgmt[Thread-974] [VsanVumConnection::_UploadBuildsAndDrivers opID=noOpId] Upload comlepeted!
2020-01-14T14:05:08.379+06:00 INFO vsan-mgmt[Thread-974] [VsanVumConnection::_LookupPatchBaseline opID=noOpId] Looking up baseline for patch VMware ESXi 6.7.0 U3 (Patch
ESXi670-Update03) with vSAN recommended patches ESXi670-201912001 (keys: [], hash: None)...
2020-01-14T14:05:08.379+06:00 INFO vsan-mgmt[Thread-974] [VsanVumCoreUtil::QueryBaselinesForUpdatefun opID=noOpId] Query baseline for update []
2020-01-14T14:05:08.380+06:00 INFO vsan-mgmt[Thread-974] [VsanVumCoreUtil::retryWrapper opID=noOpId] failed with VUM exception Required field "update" not provided (not
@optional)
2020-01-14T14:05:08.380+06:00 ERROR vsan-mgmt[Thread-974] [VsanVumConnection::RemediateAllClusters opID=noOpId] Failed to remediate cluster 'vim.ClusterComputeResource:
domain-c66'
Traceback (most recent call last):
File "/usr/lib/vmware-vpx/vsan-health/pyMoVsan/VsanVumCoreUtil.py", line 150, in retryWrapper
return f(self, *args)
File "/usr/lib/vmware-vpx/vsan-health/pyMoVsan/VsanVumCoreUtil.py", line 234, in QueryBaselinesForUpdatefun
result = bm.QueryBaselinesForUpdate(update = update)
File "/usr/lib/vmware/site-packages/pyVmomi/VmomiSupport.py", line 557, in <lambda>
self.f(*(self.args + (obj,) + args), **kwargs)
File "/usr/lib/vmware/site-packages/pyVmomi/VmomiSupport.py", line 362, in _InvokeMethod
list(map(CheckField, info.params, args))
File "/usr/lib/vmware/site-packages/pyVmomi/VmomiSupport.py", line 887, in CheckField
raise TypeError('Required field "%s" not provided (not @optional)' % info.name)
TypeError: Required field "update" not provided (not @optional)
Traceback (most recent call last):
File "/usr/lib/vmware-vpx/vsan-health/pyMoVsan/VsanVumConnection.py", line 1595, in RemediateAllClusters
self.RemediateVsanClusterInVum(vvchs, cluster)
File "/usr/lib/vmware-vpx/vsan-health/pyMoVsan/VsanVumConnection.py", line 1329, in RemediateVsanClusterInVum
patchNames, patchIds)
File "/usr/lib/vmware-vpx/vsan-health/pyMoVsan/VsanVumConnection.py", line 1184, in _CreatePatchBaselines
self.CreateBaselineFromOfficialPatches(patchName, patchIds)
File "/usr/lib/vmware-vpx/vsan-health/pyMoVsan/VsanVumConnection.py", line 416, in CreateBaselineFromOfficialPatches
baseline = self._LookupPatchBaseline(name, keys)
File "/usr/lib/vmware-vpx/vsan-health/pyMoVsan/VsanVumConnection.py", line 454, in _LookupPatchBaseline
result = self.QueryBaselinesForUpdate(update = updateKeys)
File "/usr/lib/vmware-vpx/vsan-health/pyMoVsan/VsanVumCoreUtil.py", line 237, in QueryBaselinesForUpdate
return self.retryWrapper(QueryBaselinesForUpdatefun, update)
File "/usr/lib/vmware-vpx/vsan-health/pyMoVsan/VsanVumCoreUtil.py", line 163, in retryWrapper
assert(False)
AssertionError
2020-01-14T14:05:08.381+06:00 INFO vsan-mgmt[Thread-974] [VsanVumSystemUtil::GetConfigIssueIds opID=noOpId] Get config issue id ['health.test.vum.createBaselineFailed'] for entity domain-c66
2020-01-14T14:05:08.382+06:00 INFO vsan-mgmt[Thread-974] [VsanVumSystemUtil::AddConfigIssue opID=noOpId] Skip create baseline failure when there is other issues
Resolution
Pre-checks to be done:
The vCenter should have internet connectivity:
root@vCenterServer# wget http://www.vmware.com
--2020-01-14 13:24:14-- http://www.vmware.com/
Resolving www.vmware.com...
Connecting to www.vmware.com|10.x.x.x|:80... connected.
VUM download settings are available Path : Home> Update manager> Manage Tab> Settings > download settings. Customer can chose to disable Auto-download of patches if base line creation is not needed.
https://docs.vmware.com/en/VMware-vSphere/6.7/com.vmware.vsphere.update_manager.doc/GUID-D53B8D36-A8D7-4B3B-895C-929267508026.html
KB reference: https://kb.vmware.com/s/article/2150914
Workaround:
The vCenter should have internet connectivity:
root@vCenterServer# wget http://www.vmware.com
--2020-01-14 13:24:14-- http://www.vmware.com/
Resolving www.vmware.com...
Connecting to www.vmware.com|10.x.x.x|:80... connected.
VUM download settings are available Path : Home> Update manager> Manage Tab> Settings > download settings. Customer can chose to disable Auto-download of patches if base line creation is not needed.
https://docs.vmware.com/en/VMware-vSphere/6.7/com.vmware.vsphere.update_manager.doc/GUID-D53B8D36-A8D7-4B3B-895C-929267508026.html
KB reference: https://kb.vmware.com/s/article/2150914
Workaround:
- Manually upload the patch ESXi670-201912001 that was reported as missing in vSAN health service logs to VUM. (Home> Update manager> Manage Tab> Patch repository > Upload File)
- The patch uploaded to the VUM repository will meet the need of vSAN default baselines.
- After the patch is uploaded the user can create customer base lines and upgrade the hosts. User must ensure if the patch is compatible to ESXIi Hosts.
Additional Information
Impact/Risks:
No impact to the environment.
No impact to the environment.
Feedback
Yes
No
Powered by
