Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

Unexpected VMware Update Manager (VUM) baseline creation failure. (76871)

Last Updated: 6/8/2023Categories: TroubleshootingTotal Views: 17775Language:
Chinese (Simplified)JapaneseEnglish

2 like this article

Subscribe to get an email
newsletter with new updates

2 people found this helpful Please provide article feedback:

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.

Purpose

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.

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

Impact / Risks

No impact to the environment.

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

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.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)JapaneseEnglish

Attachments

Additional Resources

No results for undefined

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vSAN

Related Versions:

VMware vSAN 6.x

Take Our Survey

Support Assistant