Workload Domain deployment fails with "Failed to get install image(s) for product" error

Products

VMware SDDC Manager / VCF Installer

Issue/Introduction

This article provides resolution steps when a Workload Domain deployment halts because the SDDC Manager cannot find or fetch the required ESXi or vCenter install images.

UI error: Failed to get installed image(s) for product.

var/log/vmware/vcf/domainmanager/domainmanager.log

YYYY-MM-DDThh:mm:ss INFO [vcf_dm,681da52b76b4e3449f2aab39be78d14a,5b21] [c.v.e.s.c.s.a.i.ImageManagementServiceAdapterImpl,dm-exec-2] Getting image specs from http://localhost:80
YYYY-MM-DDThh:mm:ss DEBUG [vcf_dm,681da52b76b4e3449f2aab39be78d14a,5b21] [c.v.e.s.c.s.a.i.ImageManagementServiceAdapterImpl,dm-exec-2] Got 0 install image(s) for product VCENTER with version 8.0.3.00300-24305161 from LCM API
YYYY-MM-DDThh:mm:ss DEBUG [vcf_dm,681da52b76b4e3449f2aab39be78d14a,5b21] [c.v.e.s.c.s.a.i.ImageManagementServiceAdapterImpl,dm-exec-2] Got 0 install image(s) for product ESX with version 8.0.3-24280767 from LCM API
YYYY-MM-DDThh:mm:ss DEBUG [vcf_dm,681da52b76b4e3449f2aab39be78d14a,5b21] [c.v.e.s.c.s.a.i.ImageManagementServiceAdapterImpl,dm-exec-2] Got 1 install image(s) for product NSX_T_MANAGER with version 4.2.1.0.0-24304122 from LCM API
YYYY-MM-DDThh:mm:ss INFO [vcf_dm,681da52b76b4e3449f2aab39be78d14a,5b21] [c.v.e.s.c.s.a.i.ImageManagementServiceAdapterImpl,dm-exec-2] Got VCENTER product version for new Workload Domain: 8.0.3.00300-24305161
YYYY-MM-DDThh:mm:ss ERROR [vcf_dm,681da52b76b4e3449f2aab39be78d14a,5b21] [c.v.e.s.o.model.error.ErrorFactory,dm-exec-2] [######] MISSING_INSTALL_IMAGES_FOR_PRODUCT Failed to get install image(s) for product VCENTER with version 8.0.3.00300-24305161.
com.vmware.evo.sddc.orchestrator.exceptions.OrchTaskException: Failed to get install image(s) for product VCENTER with version 8.0.3.00300-24305161.
at com.vmware.evo.sddc.common.services.actions.ImageManagementAction.lambda
$validateExpectedImagesWereFetched$2(ImageManagementAction.java:141)
at java.base/java.lang.Iterable.forEach(Iterable.java:75)

..................................................................................................................................................................................................................................................................................................................................................................................................................................................................

YYYY-MM-DDThh:mm:ss ERROR [vcf_dm,69b32c03a9631a9f88e62ab448585afb,b0f1] [c.v.e.s.c.s.a.i.ImageManagementServiceAdapterImpl,dm-exec-4] No images found for Product ESX Version 8.0.3-24280767
YYYY-MM-DDThh:mm:ss ERROR [vcf_dm,69b32c03a9631a9f88e62ab448585afb,b0f1] [c.v.e.s.o.model.error.ErrorFactory,dm-exec-4] [#####] FAILED_TO_FETCH_IMAGES Failed to fetch the images from LCM Service with error: No images found for Product ESX Version 8.0.3-24280767.
com.vmware.evo.sddc.orchestrator.exceptions.OrchTaskException: Failed to fetch the images from LCM Service with error: No images found for Product ESX Version 8.0.3-24280767.
at com.vmware.evo.sddc.common.services.actions.ImageManagementAction.execute(ImageManagementAction.java:104)

Environment

SDDC manager 5.x

Cause

A mismatch between the Bundle ID in the SDDC Manager database and the actual directory on the NFS mount, often caused by stale or corrupted download metadata.

Resolution

As a workaround for this issue, the corrupted bundle must first be cleaned up, the download re-initiated, and the ISO file manually moved to the correct directory.

Note: Before proceeding, verify that the NSX TEP IP pool is correctly configured and has sufficient IP addresses, as validation failures here can precede image fetch errors.

Step 1: Clean up the corrupted Bundle

Run the Bundle Cleanup Utility (bundle_cleanup.py) as outlined in KB How to clean up old/ installed bundles in SDDC manager using Bundle Cleanup Utility to delete the corrupted bundle from the SDDC Manager.

Step 2: Re-download the bundle

Once the cleanup is complete, initiate the download for the required bundle again through the SDDC Manager.
Note: Initiating this download prompts the SDDC Manager to automatically create a new, dedicated directory for this specific bundle within the /nfs/vmware/vcf/nfs-mount/ path.

Step 3: Identify the new Bundle ID.

The unique ID of the newly downloaded bundle is required to place the ISO file in the correct location

Login to SDDC Manager UI
Navigate to Lifecycle Management> Bundle Management
Locate the downloaded bundle, click View Details, and note the Bundle ID (the format will be similar to bundle-####). This ID corresponds exactly to the name of the directory created in Step 2 (Re-download the Bundle)

Step 4: Verify the directory and move the ISO file

Connect to the SDDC Manager via SSH (vcf > su > root)
Verify that the directory was successfully created by the system using command ls -l /nfs/vmware/vcf/nfs-mount/
Move the ISO file from the update repository to the newly created bundle directory using the Bundle ID noted in Step 3 (Identify the new Bundle ID)
mv /<path_to_update_repo_dir>/<ISO_File> /nfs/vmware/vcf/nfs-mount/<Bundle_ID>/
Verify that the ISO file has been successfully moved into the correct directory, ls -l /nfs/vmware/vcf/nfs-mount/<bundle-####>