inprogress"** state for an extended period and eventually fails./var/log/vmware/vcf/lcm/lcm-debug.log file contains errors similar to: YYYY-MM-DDTHH:MM:SS.269+0000 ERROR [vcf_lcm,0000000000000000,0000] [c.v.e.s.l.s.i.BundleDownloadExceptionHandlerImpl,Bundle-Downloader-1] Bundle download failedcom.vmware.evo.sddc.lcm.model.depot.exception.DepotConnectionFailureException: Error downloading bundle /COMP/VCENTER/VMware-VCSA-all-9.1.0.0.25370922.iso from 10.243.25.45:80 at com.vmware.evo.sddc.lcm.bundle.download.depot.DepotBundleDownloadServiceImpl.downloadFile(DepotBundleDownloadServiceImpl.java:614) at com.vmware.evo.sddc.lcm.bundle.download.depot.DepotBundleDownloadServiceImpl.getDedupBundle(DepotBundleDownloadServiceImpl.java:764) at com.vmware.evo.sddc.lcm.bundle.download.depot.DepotBundleDownloadServiceImpl.getDedupBundle(DepotBundleDownloadServiceImpl.java:518) at com.vmware.evo.sddc.lcm.core.scheduler.BundleDownloadScheduler.performBundleDownload(BundleDownloadScheduler.java:474) at com.vmware.evo.sddc.lcm.core.scheduler.BundleDownloadScheduler.lambda$bundleDownloadTask$0(BundleDownloadScheduler.java:335) at java.base/java.util.concurrent.CompletableFuture$AsyncRun.run(CompletableFuture.java:1804) at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1144) at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:642) at java.base/java.lang.Thread.run(Thread.java:1583)Caused by: com.vmware.evo.sddc.lcm.model.error.LcmException: Timedout while waiting for data: at com.vmware.evo.sddc.lcm.bundle.download.depot.DepotDownloader.downloadFile(DepotDownloader.java:879) at com.vmware.evo.sddc.lcm.bundle.download.depot.DepotBundleDownloadServiceImpl.downloadWithRetry(DepotBundleDownloadServiceImpl.java:2239) at com.vmware.evo.sddc.lcm.bundle.download.depot.DepotBundleDownloadServiceImpl.downloadFile(DepotBundleDownloadServiceImpl.java:552) ... 8 common frames omittedVCF 9.1
This issue occurs when the local HTTP/IIS server hosting the bundles has a shorter timeout period than required for transferring large VCF binary files. The SDDC Manager's Life Cycle Management (LCM) service waits for the data, but the connection is terminated by the source server before the transfer completes, leading to a socket timeout.
To resolve this issue, increase the timeout limits on the local depot server and clear the stuck tasks on the SDDC Manager.
Step 1: Adjust Timeout on Local Depot (IIS Example)
1. Log in to the **IIS File Server** hosting the local depot.
2. Open the **IIS Manager**.
3. Select the site hosting the VCF bundles.
4. Under **Manage Website**, click on **Advanced Settings**.
5. Expand **Connection Limits** and increase the **Connection Timeout** (e.g., to 7200 seconds or 2 hours).
6. Adjust the timeout settings for the associated **Application Pool** as well.
Step 2: Clear Stuck Tasks on SDDC Manager
1. SSH into the **SDDC Manager VM** as the `vcf` user and switch to `root`.
2. Run the following command to delete stuck task registrations:
```bash
curl -s -X DELETE localhost/tasks/registrations/
Step 3: Restart LCM Services
1. Restart the SDDC Manager operations services to refresh the LCM state:
```bash
/opt/vmware/vcf/operationsmanager/scripts/cli/sddcmanager_restart_services.sh
Step 4: Retry Download
1. Return to the **SDDC Manager UI**.
2. Navigate to **Bundle Management**.
3. Locate the failed bundles and click **Retry Download**.
Impact/Risks
* Restarting SDDC Manager services will temporarily make the SDDC Manager UI unavailable (typically 5–10 minutes).
* Ensure there is sufficient disk space on the local depot server and the SDDC Manager (`/nfs/vmware/vcf/nfs-mount`) before retrying.