LCM Upgrade Precheck Fails with "Upload Required Bundles to vCenter" during VCF 9.1.x Upgrade

Products

• VMware SDDC Manager / VCF Installer

Issue/Introduction

During the upgrade of VMware Cloud Foundation (VCF) from 9.0.x to 9.1.x (or applying maintenance patches like 9.1.0.0100), the LCM upgrade precheck fails under the domain/cluster task Upload Required Bundles to vCenter.

• The SDDC Manager UI displays the following error:

Resource Name: ######vcfmgt

Description: Ensure the ESXi image bundle and NSX bundle are successfully uploaded to the vCenter Server before proceeding with the upgrade.

Impact: High - Upload failure prevents further upgrade steps. Do not proceed until this issue is resolved.

Result: An error occurred during the upload of the upgrade bundle.

Remediation: Ensure that the bundle has been successfully uploaded to the vCenter and that vCenter itself is accessible. Next, check that all the critical services, specifically vpxd, envoy-service, and updatemgr are running on vCenter by using the command service-control --status <service name>. If any of these services are stopped, you must start them using the command service-control --start <service name>. If the problem persists after completing these checks, contact Broadcom Technical Support.

• Checking the SDDC Manager /var/log/vmware/vcf/lcm/lcm-debug.log file reveals errors similar to the following:
      ERROR [vcf_lcm,...] [c.v.e.s.l.s.u.i.UmdsDownloadServiceImpl,...] URL https://<Fleet-Manager-FQDN>/depot-service/content-gateway/PROD/COMP/ESX_HOST/main/vmw-depot-index.xml already exists
      ERROR [vcf_lcm,...] [c.v.e.s.l.s.u.i.UmdsDownloadServiceImpl,...] URL https://<Fleet-Manager-FQDN>/depot-service/content-gateway/PROD/COMP/ESX_HOST/patch-store/hostupdate/__hostupdate20-consolidated-index__.xml already exists
  
  
• Checking the vCenter Server /var/log/vmware/vmware-upgrademgr/vum-server/log/vmware-vum-server.log file shows a duplicate depot entry/ID rejection:{"errorMessageId":"com.vmware.vcIntegrity.lifecycle.depots.offline.AlreadyExists","errorMessage":"Offline depot content already exists with ID '#########################'."}

 

Environment

VCF 9.1

Cause

This issue occurs when an earlier bundle upload attempt failed or was interrupted, leaving remnant offline depot IDs or XML index files registered in the vCenter vLCM database/patch store.

When subsequent prechecks or auto-retries are triggered, SDDC Manager attempts to re-register the same bundle metadata with vCenter. vCenter's vLCM service enforces unique constraint checks and rejects the registration, throwing an AlreadyExists exception.

Resolution

Since the required ESXi upgrade bundle content and metadata already exist and are intact inside the vCenter Server (which is why vCenter returns AlreadyExists), the target ESXi image is actually present and ready for remediation.

You can safely bypass/ignore the precheck result and proceed directly with the ESXi host upgrade using one of the following methods:

• In SDDC Manager UI, navigate to Lifecycle Management > Updates/Upgrades.

• Expand the failed precheck task Upload Required Bundles to vCenter.

• If available, click Silence or Acknowledge in the top-right corner of the error details pane.

• Once acknowledged, click Schedule Upgrade or Upgrade Now to continue upgrading the ESXi hosts.