Unable to import HPE bundle to vCenter Lifecycle Manager

Products

• VMware vCenter Server

Issue/Introduction

• Offline bundle import fails with error HostPatchOutdatedMetadataImport
  
  
  
  
• vCenter /var/log/vmware/vmware-updatemgr/vum-server/vmware-vum-server.log
  
  2024-10-29T15:46:36.354+08:00 info vmware-vum-server[13150] [Originator@6876 sub=ConfirmOfflinePatchTask.ConfirmOfflinePatchTask{214}] [vciTaskBase 689] Task started...
2024-10-29T15:46:36.384+08:00 error vmware-vum-server[13150] [Originator@6876 sub=HostUpdateDepotManager] [metadataCache 148] Importing outdated bulletin: VMware-vmkusb_0.1-7vmw.703.0.50.20036589 <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<---------- This component "vmkusb" is causing the issue as per this scenario
2024-10-29T15:46:36.385+08:00 warning vmware-vum-server[13150] [Originator@6876 sub=ConfirmOfflinePatchTask.ConfirmOfflinePatchTask{214}] [confirmOfflinePatchTask 214] Confirm Offline Patch received with exception outdated bulletin
2024-10-29T15:46:36.452+08:00 error vmware-vum-server[13145] [Originator@6876 sub=com.vmware.vcIntegrity.lifecycle.CreateOfflineDepotTask] [Task, 511] Task:com.vmware.vcIntegrity.lifecycle.CreateOfflineDepotTask ID:5277f00f-e243-a5af-f0dc-d11bbefdb7be. Task Failed. Error: Error:
-->    com.vmware.vapi.std.errors.error
--> Messages:
-->    com.vmware.vcIntegrity.lifecycle.depots.offline.ConfirmOfflinePatchTaskErrorInfo<Confirm importing offline patches task failed while creating offline depot. Error: 'integrity.fault.HostPatc
hOutdatedMetadataImport: Cannot import patch details. There are no new bulletins or software packages to import.'.>
-->
2024-10-29T15:46:36.453+08:00 warning vmware-vum-server[13925] [Originator@6876 sub=TaskStatsCollector] [taskStatsCollector 190] Task type or creation time not present
2024-10-29T15:46:36.453+08:00 info vmware-vum-server[13145] [Originator@6876 sub=PM.AsyncTask.CreateOfflineDepotTask{212}] [vciTaskBase 1496] SerializeToVimFault fault:
--> (vmodl.fault.SystemError) {
-->    faultCause = (vmodl.MethodFault) null,
-->    faultMessage = (vmodl.LocalizableMessage) [
-->       (vmodl.LocalizableMessage) {
-->          key = "com.vmware.vcIntegrity.lifecycle.depots.offline.ConfirmOfflinePatchTaskErrorInfo",
-->          arg = (vmodl.KeyAnyValue) [
-->             (vmodl.KeyAnyValue) {
-->                key = "1",
-->                value = "integrity.fault.HostPatchOutdatedMetadataImport: Cannot import patch details. There are no new bulletins or software packages to import."
-->             }
-->          ],

Environment

vCenter Server 7.x
vCenter Server 8.x

Cause

This issue happens if an online/offline depot already exists in the Lifecycle manager repository with the same component.

The depot with the newer timestamp is loaded first. Then when loading the second depot, since the same bullein exists but is not identical, the timestamp of the depot is compared to decide which is newer version. Due to the second depot having an older time stamp, the bulletin is rejected.

Resolution

Option 1

1. Take a snapshot of vCenter VM. If the vCenter is a part of ELM, refer to KB VMware vCenter in Enhanced Linked Mode pre-changes snapshot (online or offline) best practice.
   
   
2. SSH to the vCenter via root
   
   
3. Enter Appliance Shell
   
   appliancesh
   
   
4. When prompted, enter the root password
   
   
5. List all offline and online depots
   
   dcli com vmware esx settings depots offline list
dcli com vmware esx settings depots online list
   
   
6. Check depot contents
   
   dcli com vmware esx settings depots offline content get --depot <depot UUID>
dcli com vmware esx settings depots online content get --depot <depot UUID>
   
   
7. Check which depots contain the mentioned depot in the log and remove the ones which contain this component
   
   dcli com vmware esx settings depots offline delete-task --depot <depot UUID>
dcli com vmware esx settings depots online delete-task <depot UUID>
    
   Example
   VMware-vmkusb_0.1-7vmw.703.0.50.20036589
   
   
8. Restart vum service
   
   service-control --restart updatemgr

Option 2

Alternatively, reset the VUM database if the existing baselines/depots are not needed. Refer to KB Resetting the VMware Update Manager Database.