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

VIBs "have unequal values of the 'payloads' attribute" while performing Update Manager compliance check (59257)

Last Updated: 4/3/2023Categories: TroubleshootingTotal Views: 35089Language:
Chinese (Simplified)JapaneseEnglish

22 like this article

Subscribe to get an email
newsletter with new updates

22 people found this helpful Please provide article feedback:

Learn how VMware Skyline Advisor and Skyline Health Diagnostics work together to provide proactive intelligence and self-service log analysis.

Use Skyline Advisor to avoid issues before they occur across VCF, vSphere, vSAN, NSX, vROps & Horizon. Skyline Findings are based on top KBs, VMSAs/CVEs and design best practices.

Use Skyline Health Diagnostics to root cause vSphere & vSAN logs when an issue occurs. Skyline Health Diagnostic Findings are based on top KBs and VMSA/CVEs. You can use the Skyline Health Diagnostics tool in online or offline mode.

If you require additional help from technical support, please use Skyline Advisor to initiate a Log Assist to reduce time to upload logs. TSEs can also initiate logs to reduce effort.

Symptoms

While performing an Update Manager compliance check, the scan returns the error:

esxupdate error codes: -1. Check the Update Manager log files and esxupdate log files for more details.

In the /var/run/log/esxupdate.log, you see entries similar to:

ERROR: ValueError: VIBs ELX_bootbank_elx-esx-libelxima.so_12.0.1108.0-03 and ELX_bootbank_elx-esx-libelxima.so_12.0.1108.0-03 have unequal values of the 'payloads' attribute: '[elx-esx-libelxi: 1602.936 KB]' != '[elx-esx-libelxi: 1493.833 KB]'

Image Builder is unable to build an ISO out of the software depot because it sees two sizes of the VIBs and are unable to merge. You will see similar entries in vmon-redirect.log.stderr as mentioned below:

vmon-redirect.log.stderr:
INFO:DepotCollection:Error parsing metadata.zip from https://hostupdate.vmware.com/software/VUM/PRODUCTION/main/esx/vmw/vmw-ESXi-6.7.0-metadata.zip: Cannot merge VIBs ELX_bootbank_elx-esx-libelxima.so_12.0.1108.0-03, ELX_bootbank_elx-esx-libelxima.so_12.0.1108.0-03 with unequal payloads attributes: ([elx-esx-libelxi: 1493.833 KB], [elx-esx-libelxi: 1602.936 KB])
Exception in thread Connect-task-11784841:
Traceback (most recent call last):
File "/usr/lib/python2.7/threading.py", line 801, in __bootstrap_inner
self.run()
File "/usr/lib/python2.7/threading.py", line 754, in run
self.__target(*self.__args, **self.__kwargs)
File "/usr/lib/vmware-imagebuilder/site-packages/imagebuilder/vmodl_impl/DepotManager.py", line 288, in _connectToDepot
if errors:
UnboundLocalError: local variable 'errors' referenced before assignment

Purpose

This article is to identify and resolve "have unequal values of the 'payloads' attribute" error.

Cause

This issue is caused by a VIB installed on the ESXi having a different payload value (size variants) than would be expected according to the information in its metadata.

VIB Name: ELX_bootbank_elx-esx-libelxima.so_12.0.1108.0-03

Impact / Risks

This issue will prevent the ESXi host from being able to be patched.

Host baselines for critical and non-critical patches will show non-compliant all the time.

Resolution

To resolve this issue, remove the conflicting VIB and perform the patch update again. For more information on removing VIBs, see Remove VIBs from a Host.

Note: Before removing the conflicting VIB, confirm it is not in use on the host. For more information, see Determining Network/Storage firmware and driver version in ESXi

For example in case of elx-esx-libelxima.so VIB with unequal payload:

esxcli software vib remove -n elx-esx-libelxima.so

Workaround

Manually install http://vibsdepot.hpe.com/hpe/sep2018/esxi-670-devicedrivers/VMW-ESX-6.7.0-elxiscsi-12.0.1108.0-8119170.zip on the impacted ESX host by esxcli (not scalable if there are many hosts).

Remove the HPE depot, reset VUM DB/patch store, and resume to only import the needed monthly release (http://vibsdepot.hpe.com/hpe/sep2018/index.xml), create a baseline and remediate the impacted host. This will mean redoing things from VUM side. Afterward you will need to reset VUM again and re-import the whole HPE depot to resume getting the latest contents.

Note: This workaround is to get the host updated with this one VIB and move on to new updates in the future. Once installed the unequal error will not appear since the VIB is no longer needed to be applied.

Create a custom baseline without the conflicting VIB.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)JapaneseEnglish

Attachments

Additional Resources

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

KB
•
Recommended paths for identifying and activating drive LEDs on HPE server platforms (56968)

KB
•
Download and Install VMware Fusion (2014097)

Results 1-3 of 3

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vSphere Update Manager

VMware vSphere

VMware Update Manager

ESXi

Related Versions:

Take Our Survey

Support Assistant