"Unexpected VMware Update Manager (VUM) baseline creation failure" error in vSAN Build Recommendation Engine Health

Products

• VMware vSAN

Issue/Introduction

Symptoms:

• When navigating to vSAN Health > vSAN Build Recommendation Engine Health, you see an error similar to:

Unexpected VMware Update Manager (VUM) baseline creation failure. Please check vSAN and VUM logs for details.

• vSAN system managed baseline exists in Update Manager baseline view.
• In the /var/log/vmware/vsan-health/vmware-vsan-health-service.log file, you see the entries similar to:

2019-07-09T10:06:31.473Z ERROR vsan-health[Thread-43] [VsanVumConnection::RemediateAllClusters] Failed to remediate cluster 'vim.ClusterComputeResource:domain-c9219'
Traceback (most recent call last):
  File "/usr/lib/vmware-vpx/vsan-health/pyMoVsan/VsanVumConnection.py", line 1075, in RemediateAllClusters
    performScan = performScan)
  File "/usr/lib/vmware-vpx/vsan-health/pyMoVsan/VsanVumConnection.py", line 862, in RemediateVsanClusterInVum
    self.Upload(patchOnly=patchOnly)
  File "/usr/lib/vmware-vpx/vsan-health/pyMoVsan/VsanVumConnection.py", line 200, in Upload
    self.UploadEsxImages(isoBasedEsxImages)
  File "/usr/lib/vmware-vpx/vsan-health/pyMoVsan/VsanVumConnection.py", line 315, in UploadEsxImages
    isoName = build['isoDisplayName']
KeyError: 'isoDisplayName'
2019-07-09T10:06:31.473Z INFO vsan-health[Thread-43] [VsanVumSystemUtil::AddConfigIssue] Add config issue createBaselineFailed
Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.

• vCenter is running on version 6.5.
• ESXi hosts in the vSAN cluster are using controllers that are currently not on the vSAN HCL listed for the latest version of vSAN 6.5U3.
• Resetting the VMware Update Manager database via the below KB does not resolve the issue. 

           Resetting VMware Update Manager Database on a vCenter Server Appliance 6.5/6.7/7.0 (2147284)

Environment

VMware vSAN 6.5.x
VMware vSAN 6.6.x

Cause

The vSAN build recommendation engine is building the system managed baseline against the latest version of the release of the vCenter, as described in the document Administering VMware vSAN (p105) and the storage controllers used in the vSAN hosts.

The issue appears if the storage controller is not listed on the vSAN HCL for the latest build of ESXi. This can be verified by checking the vSAN HCL.

Resolution

This issue has been resolved with VUM Build Recommendation Engine release catalog version 1.0.17.

Additional Information

To be alerted when this article is update, click Subscribe to Article in the Actions box.