Unsolved
This post is more than 5 years old
7 Posts
0
368078
OMSA (Dell Open Manage) stops working after installing ESXi510-201404401-BG Update
Hello,
We searched if someone already reported this error, in the community forums and in the global community and we didn't found any lead to solve it.
When deploying a couple of ESXi 5.1 hypervisors and patching them with the last available updates we stumble into this problem that is crippling a little bit our deployments and some functionalities provided by the OMSA (Dell OpenManage plugin).
The issue seemed to be related to a specific patch:
ESXi510-201404401-BG Update
When we applied this patch/update the OMSA 7.4 cim stops working and when we try to login into the "hypervisor OMSA" using the dell OpenManage server Administrator the end result is "Login Failed".
So the ESXi build level that it is working for us is 1743201
After patching it with ESXi510-201404401-BG, it became 1743533 and omsa stop working as expected.
To troubleshoot if it was a problem with a specific OMSA vib version or not, we tried to reinstall OMSA vib versions 7.4, 7.3, 7.2 and 7.1 always with the same end result.
We checked the logs of OMSA and ESXi and it seem everything all right and the authentication seem to go through.
We compared the relevant config files between a working one and a non-working hypervisor in the "omsa installation" and besides the expected differences nothing points to a smoking a gun in there.
Please let us know if there is anything that we can look for to extend the troubleshoot and trying to find a fix/workaround to get this back on tracks.
Thank you,
Ricardo
rpardini
3 Posts
0
June 6th, 2014 10:00
I can't find 5.5U2 anywhere yet, is it released?
For now I will keep 5.1 1612806, it seems it is not Heartbleed-vulnerable after all.
bvig-gd
4 Posts
0
June 6th, 2014 10:00
Sup3rFly
12 Posts
0
June 17th, 2014 10:00
Thanks for update.
It's ridiculous the number of issues I've had with OMSA being reliable with ESXi 4.1 and 5.1 over the years. I've given up.
radao
7 Posts
0
June 18th, 2014 08:00
Yes it seems to be solving the issue.
I've tested it this morning in a couple of hypervisors and it worked.
I thought that was something related with the XML parsing.
In the patch that broke the OMSA in the beginning there was some "update/patch" to the WSMAN related to the XML parsing and now they fixed something in the XML handling in the WSMAN and seems to solve the issue.
Hope that this is usefull.
bwilliam14
1 Message
0
June 18th, 2014 08:00
I just received an email from VMware noting this:
http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2077641
Anyone know if this fixes this particular issue? I assumed the 3rd note in the release notes having to do with characters in the XML was the issue.
T. York
1 Message
0
June 20th, 2014 17:00
It looks an update to ESXi 5.1 was released earlier this week (ESXi510-201406401-SG). Any indications if this fixes the issue with OMSA 7.4?
radao
7 Posts
0
June 21st, 2014 00:00
Yes,
it solved the problem with OMSA, in fact the problem was with the WSMAN not the OMSA specifically, from what I could gather.
ClaudioG64
4 Posts
0
June 23rd, 2014 09:00
Hello,
the fix is out now and it works :emotion-1:
http://kb.vmware.com/kb/2077641
Kind regards
Claudio