VCF 9.0.x Depot Sync Failure and FAILED_TO_VALIDATE_COMPONENT_FILE API Error

Products

• VMware SDDC Manager / VCF Installer

Issue/Introduction

VMware Cloud Foundation (VCF) 9.0.x Depot Sync failure resulting in API validation errors.

The metadata catalog syncs successfully via PUT /v1/system/settings/depot, but bundles remain in a PENDING download status.

This prevents the POST /v1/sddcs/validations API from completing successfully for Management Domain deployment. Executing GET /v1/bundles returns "downloadStatus": "PENDING" and "downloadedSize": 0 for required bundles.

The POST /v1/sddcs/validations API returns FAILED with nested errors stating "Failed to validate or retrieve component file" for VCF Bill of Materials (BOM) components (e.g., vCenter, NSX, SDDC Manager).

Environment

VMware Cloud Foundation 9.0.x

Cause

The SDDC Installer database successfully synced the offline depot metadata catalog, but the binary payloads (.tar/.sig) were not automatically fetched and staged on the local appliance filesystem. The validation engine requires physical access to the component binaries on the local filesystem to compute cryptographic checksums and verify BOM alignment.

Resolution

 

• Identify all pending bundles by executing the following API call: GET /v1/bundles?downloadStatus=PENDING

• Initiate the bundle downloads manually. For each required component bundle ID, execute a PATCH request: PATCH /v1/bundles/<BUNDLE_ID>

• Include the following JSON payload in the PATCH request: {"bundleDownloadSpec": {"downloadNow": true}} Note: This can be automated via a bash orchestration loop iterating over the pending bundle IDs.

• Monitor the download tasks to ensure they transition to SUCCESSFUL and the bundle state updates to DOWNLOADED.

• Once the binaries are successfully staged, execute the POST /v1/sddcs/validations API to clear the validation fault and proceed with deployment.

 

Additional Information

VMware Cloud Foundation 9.0 API Reference