SDDC Manager cluster creation workflow fails on task - "Upload vSphere Lifecycle Manager Image to vCenter Server" with error "Failed to upload Image Zip"

Products

• VMware SDDC Manager

Issue/Introduction

• Attempting to create a cluster using SDDC Manager fails on task "Upload vSphere Lifecycle Manager Image to vCenter Server" with error - 

Message: Failed to upload Image Zip [https://sddc_fqdn/vmware/vcf/personalities/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx/Content/OFFLINE_BUNDLE_xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx.zip] to vcenter.
Cause: Internal vcenter error

• The vCenter log file /var/log/vmware/vmware-updatemgr/vum-server/vmware-vum-server.log contains the error below - 

YYYY-MM-DDThh:mm:ss.xxxZ info vmware-vum-server[xxxxx] [Originator@xxxx sub=DownloadMgr] [downloadMgr xxx] Validation passed for file downloaded from: https://sddc_fqdn/vmware/vcf/personalities/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx/Content/OFFLINE_BUNDLE_xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx.zip
YYYY-MM-DDThh:mm:ss.xxxZ error vmware-vum-server[xxxxx] [Originator@xxxx sub=ServiceProvider] [EmbeddedPyServiceProvider xxxx] Failed to validate depots: /storage/updatemgr/patch-store-temp/xxxx-xxxx-xxxx-xxxx.zip

• In the corresponding personalities directory below, on the SDDC Manager - it is seen that the iso, zip and json file in that directory have an incorrect file size of 4.0 kilobytes

/nfs/vmware/vcf/nfs-mount/personalities/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx/Content

Environment

VCF 5.2.0.0

Cause

The contents of the corresponding personalities directory below, on the SDDC Manager, are corrupt.

/nfs/vmware/vcf/nfs-mount/personalities/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx/Content

Resolution

• Create a new personality on SDDC Manager based on the ESX release required - see this article for instructions on how to do this - https://knowledge.broadcom.com/external/article/311974/creating-personality-in-vcf-by-uploading.html
• After the new personality has been created on SDDC Manager - leverage this article - https://knowledge.broadcom.com/external/article?articleNumber=314620 - to -
  • Export the workflow from the SDDC Manager
  • Update the workflow file to replace the corrupted personality ID xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx with the newly created personality ID yyyyyyyy-yyyy-yyyy-yyyy-yyyyyyyyyyyy (identifiable by reviewing /nfs/vmware/vcf/nfs-mount/personalities/ for the newest directory created)
  • Inject the workflow back into the SDDC Manager
• Retry the task, the cluster is then expected to be created