Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

Creating a VI Workload domain or adding a cluster fails at 'Failed to upload Image Zip to vcenter' (78951)

Last Updated: 10/2/2020Categories: TroubleshootingTotal Views: 4232Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

The "UploadZipToVcenterAction" sub-task fails during add cluster or create VI Workload Domain workflow with DownloadFail error:

Failed to upload Image Zip [http://sddc-manager.vrack.vsphere.local:7101/vmware/vcf/personalities/ce6b4e40-706d-4f58-967d-786e08b5734a/Content/OFFLINE_BUNDLE_1500756841.zip ] to vcenter.

Visible error in the vCenter Web Client:

"An error occurred while downloading depot metadata from <image json file>"

Visible in vCenter logs:

2020-03-30T23:54:15.721Z error vmware-vum-server[40115] [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/01bc-1d6d-3bf4-2608.zip?index.xml"
]
},
"resolution": null,
"time": "2020-03-30T23:54:15.672Z"
}
]
}

Cause

The personality json file was not uploaded successfully to LCM.

Resolution

SSH to the VMware SDDC Manager VM and change to the root user:

su -

Navigate to the directory /nfs/vmware/vcf/nfs-mount/personalities/<Personality UUID>  where the PersonalityName is the one associated with the the domain/cluster being used.

Using Step 1 from this documentation, download the LCM personality zip from the vCenter Server.

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.

Make sure to keep the Offline bundle zip name the same.

Restart the create VI/ Add Cluster operation from the SDDC Manager UI.

Related Information

For determining the personality name, steps in the following document can be used to export from the vCenter Server, https://docs.vmware.com/en/VMware-Cloud-Foundation/4.0/com.vmware.vcf.admin.doc_40/GUID-3688CAC2-06E0-4422-8CFA-0332F373FD7E.html

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

KB
•
NSX の vSphere with Tanzu 展開で NCP オプション configure_t0_redistribution が True に設定されている (79392)

KB
•
Download and Install VMware Fusion (2014097)

KB
•
VMware Cloud on AWS - VMC 上で動作する仮想マシンが SDDC に接続された Amazon VPC ネットワークに接続できない (76385)

Results 1-4 of 4

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware Cloud Foundation

Related Versions:

VMware Cloud Foundation 4.x

Take Our Survey

Support Assistant