Loading

×Sorry to interrupt
This page has an error. You might just need to refresh it.
[NoErrorObjectAvailable] Uncaught ReferenceError: addCTracking is not defined
Failing descriptor: {markup://c:KM_ArticleThemeLayout}

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

After upgrading to vCenter Server 7.0.0b with vSphere Lifecycle Manager Images configuring the vSphere HA Agent fails (79388)

Last Updated: 7/3/2020Categories: TroubleshootingTotal Views: 10410Language:
English

2 like this article

Subscribe to get an email
newsletter with new updates

2 people found this helpful Please provide article feedback:

Symptoms

After upgrading to vCenter Server 7.0.0b with:

Clusters that are using vSphere Lifecycle Manager Images that are configured with vSphere HA

HPE Addon version 700.0.0.10.5.0-108

You see tasks failing similar to:

Cannot complete the configuration of the vSphere HA agent on the host.

Applying HA VIBs on the cluster encountered a failure

Cause

This issue is caused by a bad checksum of the Marvell qlnativefc driver in the depot that prevents the Marvell VIB from being downloaded, causing the Apply task to the vSphere Lifecycle Manager clusters timing out.

This can be identified in /storage/log/vmware/vmware-updatemgr/vum-server/vmware-vum-server-log4cpp.log:

[2020-05-26 12:47:42:215 'HostUpdateDepotManager' 139833857431296 ERROR]  [patchDepotManager, 500] Failed to download the vibs: https://hostupdate.vmware.com/software/VUM/PRODUCTION/addon-main/addon/HPE/vib20/qlnativefc/Marvell_bootbank_qlnativefc_4.1.9.0-1OEM.700.1.0.15525992.vib
[2020-05-26 12:47:42:229 'TaskStatsCollector' 139834339747584 WARN]  [taskStatsCollector, 192] Task type or creation time not present
[2020-05-26 12:47:42:231 'PM.AsyncTask.ClusterApplyHATask{10}' 139833857431296 INFO]  [vciTaskBase, 1343] SerializeToVimFault fault: (vmodl.fault.SystemError) {    faultCause = (vmodl.MethodFault) null,     faultMessage = (vmodl.LocalizableMessage) [       (vmodl.LocalizableMessage) {          key = "com.vmware.vcIntegrity.lifecycle.depots.VibDownloadError",           arg = <unset>,           message = <unset>       }    ],     reason = "vLCM Task failed, see Error Stack for details."    msg = "{     "data": null,     "error_type": "ERROR",     "messages": [         {             "args": [],             "default_message": "Failed to download some vib.",             "id": "com.vmware.vcIntegrity.lifecycle.depots.VibDownloadError"         }     ] }" } Converted fault: (vim.fault.ExtendedFault) {    faultCause = (vmodl.MethodFault) null,     faultMessage = (vmodl.LocalizableMessage) [       (vmodl.LocalizableMessage) {          key = "com.vmware.vcIntegrity.lifecycle.depots.VibDownloadError",           arg = <unset>,           message = <unset>       }    ],     faultTypeId = "SystemError",     data = (vim.KeyValue) [       (vim.KeyValue) {          key = "faultCause",           value = ""       },        (vim.KeyValue) {          key = "reason",           value = "vLCM Task failed, see Error Stack for details."       }    ]    msg = "{     "data": null,     "error_type": "ERROR",     "messages": [         {             "args": [],             "default_message": "Failed to download some vib.",             "id": "com.vmware.vcIntegrity.lifecycle.depots.VibDownloadError"         }     ] }" }

Resolution

To resolve this issue, update the Vendor Add-On for the affected vSphere Lifecycle Manager Image-based clusters.

Workaround

To workaround this issue, clean the HPE VIBs using the scripts provided:

Download and extract the scripts from the attached zip file 79388_remove-HPE-scripts.zip.

Copy and execute the remove-HPE.sh script on your vCenter Server Appliance.

If UMDS is in use, copy and execute the remove-umds-HPE.sh script on the machine where UMDS is installed to remove obsolete HPE addon from UMDS patch store.

After the remove-HPE.sh script automatically restarts vLCM, run Lifecycle Manager > ACTIONS > Updates > Sync Updates.

Navigate to Lifecycle Manager > Image Depot > Vendor Addons table and make sure HPE Customization for HPE Servers 700.0.0.10.5.5-46 is displayed.

Edit the desired image of existing vLCM clusters, if HPE Customization for HPE Servers 700.0.0.10.5.0-108 is configured, replace it with HPE Customization for HPE Servers 700.0.0.10.5.5-46 and then save the image.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

79388_remove-HPE-scripts

Additional Resources

KB
•
ASCII 以外のデータ ソース名を持つ WinVC 6.5 を 7.0 にアップグレードすると失敗する (79367)

KB
•
VMware Workspace ONE Assist 5.3.1 for Windows Mobile/CE リリースのお知らせ (79435)

Results 1-2 of 2

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vCenter Server

Related Versions:

VMware vCenter Server 7.0.x

Take Our Survey

Support Assistant