Symptoms:
- The content of the offline bundle does not show up in Lifecycle Manager.
- You see a message similar to:
A general system error occurred: Download patch definitions task failed while syncing depots. Error: 'integrity.fault.HostPatchInvalidVendorCode: Invalid vendor code CIS in patch metadata, another vendor code with different capitalization already exists in database. Check the Lifecycle Manager log files for more details.
- The Save or Validate operations with the image containing packages from Hardware Support Manager fail with a message similar to:
Failed to fetch component information for hardware support package VMware ESXi 7.0 Upgrade Pack in the depot, Invalid hardware support spec specified in the draft
- Importing offline bundle into vSphere Lifecycle Manager fails through the vSphere Web Client.
- You see a message similar to:
Error: 'integrity.fault.HostPatchInvalidVendorCode'
- In the /var/log/vmware/vmware-updatemgr/vum-server/vmware-vum-server-log4cpp.log file, you see a message similar to:
[2020-04-16 19:25:07:881 'HostUpdateDepotManager' 139788413433600 ERROR] [metadataCache, 319] Invalid vendor code: <VENDOR CODE>, this conflicts with the existing code: <vendor code>. Invalid code is from URL:https://hostupdate.vmware.com/software/VUM/PRODUCTION/addon-main/addon/<VENDOR CODE>
[2020-04-16 19:25:07:884 'VciSigUpdateTask.SigUpdateTask{11}' 139788413433600 ERROR] [vciSigUpdateTask, 427] Error download ESX 4x updates from https://hostupdate.vmware.com/software/VUM/PRODUCTION/addon-main/vmw-depot-index.xml: <VENDOR CODE>
Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.