VI workload domain creation/cluster expansion failed: vCenter image zip upload error.
search cancel

VI workload domain creation/cluster expansion failed: vCenter image zip upload error.

book

Article ID: 324048

calendar_today

Updated On:

Products

VMware Cloud Foundation

Issue/Introduction

  • Cluster expansion or VI Domain creation fails with 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.

     

  • The following error message was observed within the vSphere Client GUI:
    "An error occurred while downloading depot metadata from <image json file>"

     

  • The following error entries were identified in the /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"
           }
        ]
     }

Environment

VMware Cloud Foundation 4.x

Cause

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.

Resolution

  1. SSH to the VMware SDDC Manager VM and change to the root user: su -
  2. Navigate to the directory /nfs/vmware/vcf/nfs-mount/personalities/<Personality UUID>  where the PersonalityName is the one associated with the the domain or cluster being used.
  3. Using Personalities APIs , download the LCM personality zip from the vCenter Server.
  4. Using a file transfer utility, upload the file to /nfs/vmware/vcf/nfs-mount/personalities/<PersonalityName> to replace the zip file with the correct personality zip.
  5. Make sure to keep the offline bundle zip name the same.
  6. Restart the Create VI domain or  Add Cluster operation from the SDDC Manager UI.

Additional Information

To identify the personality name, please follow the export steps outlined in the attached vCenter Server document: Personalities APIs