UploadZipToVcenterAction and sub-task returned a DownloadFail error.Failed to upload Image Zip [http://sddc-manager.vrack.vsphere.local:7101/vmware/vcf/personalities/########-####-####-####-########734a/Content/OFFLINE_BUNDLE_########.zip ] to vcenter.
"An error occurred while downloading depot metadata from <image json file>"
/var/log/vmware/vsphere-updatemgr/vum-server/vum-server.log:YYYY-MM-DDTHH:MM:SS error vmware-vum-server[] [Originator@6876 sub=DepotContentManager] Depot Validation: Problems found while validating depot content: {
"info": [],
"warnings": [],
"errors": [
{
"id": "com.vmware.vcIntegrity.lifecycle.EsxImage.MetadataDownloadError",
"message": {
"id": "com.vmware.vcIntegrity.lifecycle.EsxImage.MetadataDownloadError",
"default_message": "An error occurred while downloading depot metadata from {1}.",
"args": [
"zip:/storage/updatemgr/patch-store-temp/####-####-####-####.zip?index.xml"
]
},
"resolution": null,
"time": "YYYY-MM-DDTHH:MM:SS"
}
]
}During the deployment process, the Personality JSON file, which contains the metadata and configuration specifications for the environment was not successfully uploaded to the LCM module.
This failure typically blocks the system from initializing the required cluster or workload domain.
su -/nfs/vmware/vcf/nfs-mount/personalities/<Personality UUID> where the PersonalityName is the one associated with the the domain or cluster being used./nfs/vmware/vcf/nfs-mount/personalities/<PersonalityName> to replace the zip file with the correct personality zip.To identify the personality name, please follow the export steps outlined in the attached vCenter Server document: Personalities APIs