Adding Host to Workload Domain Fails at Host Seeding Task in VCF 9.X
Article ID: 447138
Updated On:
Products
Issue/Introduction
When attempting to add a host to a workload domain in VMware Cloud Foundation (VCF), the host seeding task fails.
When manually triggering Sync Updates within vSphere Lifecycle Manager (vLCM), the following error is displayed in the vSphere Client:
A general system error occurred: "A depot is inaccessible or has invalid contents. Make sure an official depot source is used and verify connection to the depot."
The depot has been confirmed to be enabled and connected
The error below is seen in the vCenter log file /var/log/vmware/vmware-
updatemgr/vum-server/ reveals metadata parsing conflicts similar to this:imageService.log
YYYY-MM-DD hh:mm:ss,sss INFO imageService [############] [imageService ####] Error parsing zip:/storage/updatemgr/patch-store-temp/####-fc23-0876-####.zip?metadata.zip ('Esxi: 9.1.0-0.25370933', 'baseimage', "Two base images share the same releaseID: ESXi:9.1.0-0.25370933, but have different attributes: versionSpec ('<VersionSpec version: 9.1.0-0.25370933; uiString: 9.1.0.0.25370933; vcfVersion: 9.1.0.0.25370933>' != '<VersionSpec version: 9.1.0-0.25370933; uiString: 9.1.0.0.25370933>'), swPlatforms ('[{'version': '9.1', 'locale': '', 'productLineID': 'esxio'}, {'version': '9.1', 'locale': '', 'productLineID': 'embeddedEsx'}]' != '[]')")
Environment
VCF 9.X
Cause
This issue occurs due to a schema mismatch in the baseimage metadata between different versions of VMware image creation tools.
VCF 9.0 introduced the vcfVersion attribute to the baseimage metadata.
VCF 9.1 introduced the swPlatforms attribute to the baseimage metadata.
If the custom ESXi ISOs used to image/bring up the host were generated using an older version of the PowerCLI or Image Builder tools, these new attributes are stripped or missing from the metadata. When vLCM attempts to sync and compares the host's existing image metadata against the official online depot, it detects a conflict (vcfVersion and swPlatforms mismatch), causing the sync and host seeding tasks to fail
Resolution
To resolve this metadata conflict, the custom ESXi installation media must be recreated using the updated tooling that supports the new metadata schema.
Step-by-Step Fix:
Download the Correct Tooling: Ensure you are using VCF PowerCLI 9.1 (or higher, matching your target VCF environment).
Recreate the Custom ISO: Use VCF PowerCLI 9.1 to inject your required drivers/async VIBs and generate a fresh custom ESXi ISO. This ensures the vcfVersion and swPlatforms attributes are correctly written to the metadata.
Re-image the Host: Install ESXi on the target host using the newly generated ISO.
Retry the Operation: Once the host is rebuilt, retry the Sync Updates task in vLCM, and proceed with adding the host to the workload domain.
Additional Information
Feedback
