Update manager reports incompliance issues on ESXi host

Products

• VMware vCenter Server

Issue/Introduction

This article provides steps to troubleshoot incompliance issues on the ESXi host by VMware vCenter Update Manager.

Symptoms:

• Update Manager reports that the host is in compliance with the baseline.However, the baseline contains updates that have not been applied to the ESXi host.

• Update Manager marks updates as Not Applicable but the update is still valid.
  
  
• In the \ProgramData\VMware\VMware Update Manager\logs\vmware-vum-server-log4cpp.log file, you see entries similar to:

[YYYY-MM-DD TIME:950 'HostUpdateDepotManager' 532 ERROR] [scanHost20, 1905] Error while computing host patching conflict resolution suggestion for patch ESXi500-201510102-SG : ID: VMware_locker_tools-light_5.0.0-3.70.3021432 not found!

[YYYY-MM-DD TIME:950 'HostUpdateDepotManager' 532 ERROR] [scanHost20, 1905] Error while computing host patching conflict resolution suggestion for patch ESXi500-201510401-BG : ID: VMware_bootbank_esx-base_5.0.0-3.73.3086167 not found!

Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.

Environment

VMware vCenter Update Manager 4.1.x
VMware vCenter Update Manager 5.0.x
VMware vCenter Update Manager 5.5.x
VMware vCenter Update Manager 5.1.x

Cause

This issue occurs when:

• The Update Manager database is out of sync.
• The information contained within the Update Manager database is not same as information on the ESXi host filesystem.

Resolution

To resolve this issue, re-download the metadata.zip file to the patch store and re-scan the ESXi Host:

1. Navigate to the Update Manager patch store.
   
   Note: By default,location of patch store is \ProgramData\VMware\VMware Update Manager\Data\hostupdate\vmw.
   
   
2. Locate the vmw-ESXi-X.X.X-metadata.zip file, and rename it to metadata.old.
   
   
3. In vCenter Server, navigate to Update Manager under Solutions and Applications.
   
   
4. Click the Configuration tab and go to Download Settings link.
   
   
5. Click Download Now button to re-download the metadata.zip file to the patch store.
   
   
6. Confirm that the metadata.zip file gets restored to the file location found in patch store.
   
   
7. Re-scan ESXi hosts and it should now show non-compliant with the attached baseline.
   

Note: The file being renamed remains in the filesystem and is replaced with a new file that is downloaded into the repository.

Additional Information

更新 ESXi 主机上的管理器报告不符合问题