/var/log/vmware/vcf/lcm/lcmdebug.log :
YYYY-MM-DD:[main]DEBUG[com.vmware.evo.sddc.lcm.bundle.download.depot.utils.BundleUtils]Listofnotsupportedproducts:PKS,HORIZON,NSXMANAGERYYYY-MM-DD:[main]DEBUG[com.vmware.evo.sddc.lcm.bundle.download.depot.DepotBundleDownloadServiceImpl]Creatinglocalmanifestdirectory:/root/PROD2/evo/vmw/tmp/manifestsYYYY-MM-DD:[main]DEBUG[com.vmware.evo.sddc.lcm.bundle.download.depot.DepotBundleDownloadServiceImpl]Creatinglocalbundledirectory:/root/PROD2/evo/vmw/tmp/bundlesYYYY-MM-DDT[main]DEBUG[com.vmware.evo.sddc.lcm.tools.asyncpatch.AsyncPatchConfigProperties]AddedESXHOSTtosupportBundleSoftwareTypeYYYY-MM-DD:[main]DEBUG[com.vmware.evo.sddc.lcm.tools.asyncpatch.AsyncPatchConfigProperties]AddedNSX-TMANAGERtosupportBundleSoftwareTypeYYYY-MM-DD:[main]DEBUG[com.vmware.evo.sddc.lcm.tools.asyncpatch.AsyncPatchConfigProperties]AddedVCENTERtosupportBundleSoftwareTypeYYYY-MM-DDT[main]DEBUG[com.vmware.evo.sddc.lcm.tools.asyncpatch.AsyncPatchConfigProperties]AddingVXRAILtosupportBundleSoftwareTypeYYYY-MM-DD:[main]DEBUG[com.vmware.evo.sddc.lcm.tools.common.WarningsDisplayUtil]Loadedwarningmessagemapfile:WarningMessageMap.jsonYYYY-MM-DDT[main]DEBUG[com.vmware.evo.sddc.lcm.tools.common.WarningsDisplayUtil]Includewarnings:[]YYYY-MM-DD:[main]DEBUG[com.vmware.evo.sddc.lcm.tools.common.ConsoleUtil]Trial1/3YYYY-MM-DD:[main]DEBUG[com.vmware.evo.sddc.lcm.tools.common.WarningsDisplayUtil]BundleTransferUtilityToolfailedwitherror:Cannotreadthearraylengthbecause"sddcManagerDownloadedFiles"isnullYYYY-MM-DDTERROR[vcf_lcm,xxxxxxxxxxxxxxxx,xxxx][c.v.e.s.l.b.d.depot.DepotDownloader,http-nio-127.0.0.1-7400-exec-9]Errorgettingfilesize,gotresponse:409ConflictHTTP/1.12026-03-11T22:20:24.180+0000ERROR[vcf_lcm,xxxxxxxxxxxxxxxx,xxxx][c.v.e.s.l.b.d.depot.DepotDownloader,http-nio-127.0.0.1-7400-exec-9]GotHTTPerror[409]whiledownloadingmanifestindex[/COMP/SDDC_MANAGER_VCF/index.v3]fromdl.broadcom.com:443withuser<REDACTED_USER_EMAIL>
VMware Cloud Foundation 5.2.1
VMware Cloud Foundation 5.2.2
This issue occurs when the same bundle ID is present in the SDDC Manager database in a failed state.
This issue occurs when SDDC Manager attempts to download the manifest index file (/COMP/SDDC_MANAGER_VCF/index.v3) from the Broadcom depot (dl.broadcom.com:443), but the request is rejected with an HTTP 409 Conflict response. As a result, the DepotDownloader service is unable to retrieve the file size and download the required manifest, which prevents the LCM operation from proceeding.
Note: Please take a snapshot of the SDDC Manager VM before proceeding.
Navigate to the Bundle Management section in the SDDC Manager UI.
Filter the view to display only Downloaded bundles.
Select the older bundle you want to remove and note the Bundle ID.
SSH into the SDDC Manager VM and switch to the root user:
suRun the following command to clean up the bundle:
python /opt/vmware/vcf/lcm/lcm-app/bin/bundle_cleanup.py <bundle_id>After completing the cleanup, attempt the upload again. It should proceed successfully.
Collecting diagnostic information for VMware
https://knowledge.broadcom.com/external/article?articleNumber=367431
Uploading files to cases on the Broadcom Support Portal
https://knowledge.broadcom.com/external/article/140731/uploading-files-to-cases-on-the-broadcom.html