Scanning ESXi host with VUM fails after installing Dell OMSA 6.5 A02

[rothb]

Hello,

after installing the Dell OMSA 6.5 A02 VIB (esxcli software vib install -d /.../omsa.zip) I can no longer scan the Host with Update Manager. I get the error message:

The host returns esxupdate error code:99. An unhandled exception was encountered. Check the Update Manager log files and esxupdate log files for more details.

After looking in /var/log/esxupdate.log I see the following lines, which could be the Reason why the scanning of the Host fails:

2011-12-14T12:40:39Z esxupdate: esxupdate: ERROR: An unexpected exception was caught:
2011-12-14T12:40:39Z esxupdate: esxupdate: ERROR: Traceback (most recent call last):
2011-12-14T12:40:39Z esxupdate: esxupdate: ERROR:   File "/usr/sbin/esxupdate", line 216, in main
2011-12-14T12:40:39Z esxupdate: esxupdate: ERROR:     cmd.Run()
2011-12-14T12:40:39Z esxupdate: esxupdate: ERROR:   File "/build/mts/release/bora-474610/bora/build/esx/release/python-2.6-lib-zip-stage/474610/visor/pylib/python2.6/site-packages/vmware/esx5update/Cmdline.py", line 106, in Run
2011-12-14T12:40:39Z esxupdate: esxupdate: ERROR:   File "/build/mts/release/bora-474610/bora/build/esx/release/python-2.6-lib-zip-stage/474610/visor/pylib/python2.6/site-packages/vmware/esximage/Transaction.py", line 78, in DownloadMetadatas
2011-12-14T12:40:39Z esxupdate: esxupdate: ERROR:   File "/build/mts/release/bora-474610/bora/build/esx/release/python-2.6-lib-zip-stage/474610/visor/pylib/python2.6/site-packages/vmware/esximage/VibCollection.py", line 60, in __add__
2011-12-14T12:40:39Z esxupdate: esxupdate: ERROR:   File "/build/mts/release/bora-474610/bora/build/esx/release/python-2.6-lib-zip-stage/474610/visor/pylib/python2.6/site-packages/vmware/esximage/VibCollection.py", line 77, in AddVib
2011-12-14T12:40:39Z esxupdate: esxupdate: ERROR:   File "/build/mts/release/bora-474610/bora/build/esx/release/python-2.6-lib-zip-stage/474610/visor/pylib/python2.6/site-packages/vmware/esximage/Vib.py", line 625, in MergeVib
2011-12-14T12:40:39Z esxupdate: esxupdate: ERROR: ValueError: Cannot merge VIBs Dell_bootbank_OpenManage_6.5-0000, Dell_bootbank_OpenManage_6.5-0000 with unequal payloads attributes
2011-12-14T12:40:39Z esxupdate: esxupdate: DEBUG: <<<

Now I thought "Ok lets remove the VIB ("esxcli software vib remove OpenManage:6.5-000" afterwards "reboot") then everything will work again" but sadly it didn´t . The VIB is no longer listed (esxcli software vib list) but the error and log entrys stayed the same.

Someone else having the same or similar problem or know a way to get out of this mess?

Best regards,

Bjoern

[ranjitcool]

I am quite unsure, did some googling, have you checked with Dell Support if they had anything on this?

If nothing works I would simply re load ESXi :smileygrin:

[rothb]

Hello,

first of all thanks for trying helping me out.

I solved the problem by myself. The problem was not the ESXi Server rather the Update Manager had a problem. First I installed a ESXi5 VM in VMware Workstation 8 and the VM ESXi Server had the same problem than the other Server. Then i quickly uninstalled VUM and reinstalled it, with a clean VUM DB.

Afterwards everything was fine again. Even with installed OMSA Agent. Seems like anything other was causing this. Had nothing to do with OMSA VIB.

Thanks again for your help.

Regards,

Bjoern

[hellraiser]

Weird - I had exactly the same problem today, after having installed the same extension on a fresh install of ESXi 5.0 patched to latest build (515xxx) on a Dell T710 - I couldn't connect through the OM server, so I decided to re-install it thru Update Manager but when I came to scan for updates, I got error 99. Then I went home

Will have another look tomorrow, but there must be an easier way than removing the VUM DB? Mind you, OpenManage is a bag of crap at the best of times.....

Oh, you didn't happen to have the Equallogic MEM installed as well did you?

JD

[kacoru1]

I have had the exact same problem as well after installing the Dell OMSA 6.5, only I got errors during the install of the OMSA.  Now I get this error when I try to scan a host in Update Manager:

The host returns esxupdate error code:99  An unhandled exception was encountered.  Check the Update Manager log files and esxupdate log files for more details.

Aggravating.

Kristi

[hharold]

Just wanted you to know that I got the same issue and error after importing the Dell OMSA 6.5 A02 into the Update Manager Patch Repository.

After that all Scanning tasks on ESXi hosts fail. 😞

error code: 99, desc: Cannot merge VIBs Dell_bootbank_OpenManage_6.5-0000, Dell_bootbank_OpenManage_6.5-0000 with unequal payloads attributes

Even when this extension is not part of any baseline or attached to a host.

Any solutions, besides reinstalling VUM, would be very much appreciated.

Regards,

Harold

@hharold

[rothb]

Sehr geehrte Damen und Herren,

ich bin bis einschließlich 17.02.2012 nicht im Haus.

In dringenden Fällen wenden Sie sich bitte an unseren Service Desk (Tel.: 2098 oder hotline@klilu.de).

Vielen Dank.

Björn Roth

Administration

Z.E.N.works / Windows

Informationstechnologie

[steve31783]

Has anyone found a fix for this?  Experiencing the same issue. Trying to avoid a VUM rebuild

[steve31783]

FWIW... I fixed this by completely uninstalling VUM, reinstalling VUM, and reimporting the new VIB.

I did have the previously unsupported (but functional) OM 6.5 for ESXi VIB imported, and I believe that the presence of that within VUM is what lead to this issue, but that's just a hunch.

[hellraiser]

Ditto to this, I also had the older OM 6.5 installed in my Update Manager, so this may have causes issues. To be honest, it’s quick enough to re-install VUM so long as you don’t have a million hosts and profiles to deal with.

One other potentially useful bit of info – I had numerous problems getting Openmanage to work using a Windows 2003 server. When accessing the OM plugin on an ESXi 4.1 box it was very slow, and trying to connect to an ESXi 5 box resulted in “Internal error” every time. Rebuilt my Openmanage server on a Windows 2008 R2 machine, and everything now works perfectly; OM on the 4.1 machines is nice and fast, and the 5.0 machines work great too. No idea why a change of OS helps, but it does...

JD

[steve31783]

Thanks for the tip. I haven't tested OM connectivity yet, but will keep that in mind when I do later today.

[keithlammersBFS]

I ran into this issue recently, and was able to fix it up without having to do a full uninstall/re-install of VMware Update Manager, by following the steps in this article: VMware KB: Initializing the VMware vCenter Update Manager database without reinstalling it

Note that the steps in that article will wipe your VMware Update Manager database, so you'll need to re-create any custom baselines, and attach them to the hosts again before scanning.

Hope that helps anyone with the same issue!