Loading...
Loading...
In a vCenter Server 6.7 Update 1 environment with vSAN, you experience these symptoms: Generating vSAN baseline recommendation for the ESXi 6.7 Update 1 fails.vCenter Server 6.7 Update 1 is recommending ESXi 6.7.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.
This issue is resolved in ESXi670-201901001 available at Patch Download
To workaround this issue: If vCenter Server is running in offline mode and do not have internet connectivity, upload the offline release catalog to VSAN. For more information, see vSAN Health Service - vSAN Build Recommendation - vSAN release catalog up-to-date (58891).If vCenter Server is online and have internet connectivity: Open an SSH session to the vCenter Server appliance that is only managing the vSAN 6.7 Update 1 cluster.Edit the /etc/vmware-vsan-health/config.conf file to add vSAN release catalog entry with the keyword defaultmetadataurl. vSAN's config.conf file has a section for VumIntegration with enabled flag as True. Add new entry to the same section. After updating the config.conf file, the VumIntegration section should look like: [VumIntegration] enabled = True defaultmetadataurl = https://vcsa.vmware.com/ph/api/v1/results?deploymentId=2d02e861-7e93-4954-9a73-b08692a330d1&collectorId=VsanCloudHealth.6_5&objectId=0c3e9009-ba5d-4e5f6-bae8-f25ec506d219&type=vsan-updates-json Restart the vSAN management service. a. From the vSphere Web Client, browse to Administration > Deployment > System Configuration > Services > vSAN Health Service > Actions > Restart). b. From the VCSA CLI, run this command: /usr/lib/vmware-vmon/vmon-cli -r vsan-health
Click on a version to see all relevant bugs
VMware Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.