This post is more than 5 years old
8 Posts
0
5319
OpenManage 8.3.0 ESXi 6.0 bug?
I think I have found a bug.
I create Custom ISOs for ESXi 6.0 so I can include the latest drivers and the VIBs for our storage.
I created a new ISO with ESXi 6.0 Update 2 with the latest Dell OpenManage 8.3.0 VIB.
In vCenter(6.0) Update Manager, I have the Dell repo as a download source: https://vmwaredepot.dell.com/index.xml
I downloaded the OpenManage 8.3.0 VIB from here:
<ADMIN NOTE: Broken link has been removed from this post by Dell>
However, now when I run a scan of the host with Update Manager, it fails and the error in esxupdate.log:
2016-04-28T15:44:03Z esxupdate: esxupdate: ERROR: ValueError: Cannot merge VIBs Dell_bootbank_OpenManage_8.3.0.ESXi600-0000, Dell_bootbank_OpenManage_8.3.0.ESXi600-0000 with unequal payloads attributes: ([OpenManage: 7809.081 KB], [OpenManage: 7807.439 KB])
I'm seeing older version of OpenManage that had this same error and it was a bug.
Things I have done: Reinitialize VUM database, which I can then scan the hosts successfully. Once I add back in the Dell repo, it starts failing again with the above error in the esxupdate.log file.
Anyone else seeing the same thing?
OneLoveAmaru14
8 Posts
1
September 11th, 2016 17:00
The last I heard from Dell, they said they weren't going to fix this but focus on the next release. I haven't seen an 8.4 release, so as a work around, you'll have to uninstall OMSA 8.3 from all of your machines and then install it again from the repo.
Huge PITA though. Other option is to reset your vCenter VUM database and don't add back in the Dell repo. Then you'll be able to scan your hosts w/o issue again.
Thanks Dell!!!
OneLoveAmaru14
8 Posts
0
April 28th, 2016 11:00
I also compared the 8.2 VIB files from the repo and zip file, they are the exact SAME size.
OneLoveAmaru14
8 Posts
0
April 28th, 2016 11:00
I verified the issue. I compared the cross_dell-openmanage-esxi_8.3.0.ESXi600-0000.vib file from the Dell repo and then the one that comes inside of the zip file on the download page.... they are different sizes.
How do I report this bug to the developers?
DELL-Josh Cr
Moderator
Moderator
•
8.5K Posts
0
April 28th, 2016 12:00
Hi,
Will it let you manually install the vib with esxcli? https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2008939
nbeavers
3 Posts
0
May 13th, 2016 09:00
Were you able to get this issue worked out. I'm seeing the exact same thing.
cjandek
7 Posts
0
June 30th, 2016 09:00
add:
iSM was also changed without not updating the version, wrong payload:
esxupdate: esxupdate: ERROR: ValueError: Cannot merge VIBs Dell_bootbank_iSM_2.3.0.ESXi600-0000, Dell_bootbank_iSM_2.3.0.ESXi600-0000 with unequal payloads attributes: ([iSM: 256.707 KB], [iSM: 256.700 KB])
Workaround is to remove Openmanage and iSM (if installed):
esxcli software vib remove --vibname=OpenManage
esxcli software vib remove --vibname=iSM
Afterwards Vmware Update Manager scan succeeds.
cjandek
7 Posts
0
June 30th, 2016 09:00
Hi,
The problem is the payloads attributes don't match (from VMsupport):
esxupdate: esxupdate: ERROR: ValueError: Cannot merge VIBs Dell_bootbank_OpenManage_8.3.0.ESXi600-0000, Dell_bootbank_OpenManage_8.3.0.ESXi600-0000 with unequal payloads attributes: ([OpenManage: 7807.439 KB], [OpenManage: 7809.081 KB]
Looks like Dell changed the source for OpenManage_8.3.0 without incrementing the Version.
Dell schould release a new incremented version (example 8.3.1.) to solve the Problem.
additional Workaround:
Remove the outdated Openmanage 8.3.0 Version
esxcli software vib remove --vibname=OpenManage
OneLoveAmaru14
8 Posts
0
June 30th, 2016 09:00
I've had a ticket open with Dell for this issue and they told me they are NOT going to release an incremental version to fix this issue, they are just going to focus on the next release.
Manually running an uninstall on 100+ hosts isn't an option.
Thanks Dell!
OneLoveAmaru14
8 Posts
0
June 30th, 2016 10:00
What I did to fix my issue was resetting the VUM database and not putting the dell repo back in. That allowed Update Manager to successfully scan again.
When the new version comes out, i'll add it back in to upgrade all of my hosts.
cjandek
7 Posts
1
June 30th, 2016 10:00
Good point, thank you.
I wanted to check for new dell packages and ran into the issue.
Friendly VMsupport technician directed me to your post.
cjandek
7 Posts
0
June 30th, 2016 10:00
Wow, that's hard .... especially as it is a known BUG and the first post was 2 month ago!
Thank you for the update
Was just about to open a ticket with Dell.
... so have to wait for updates ...
drew_reis
1 Message
1
July 11th, 2016 15:00
I just ran into this issue again this morning. Are the dell technicians not watching these posts?