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
DELL-Josh Cr
Moderator
Moderator
•
8.5K Posts
0
May 8th, 2014 09:00
Hi Ricardo,
Thanks for the information. We will look into this issue. What server models is this happening on?
radao
7 Posts
0
May 8th, 2014 10:00
Hello Josh,
As explained above, we tryed to install OMSA 7.1,7.2,7.3 and 7.4 always from a clean sheet.
So the process was:
- uninstall the vib
- reboot hyp
- install vib
- reboot hyp
- test omsa
we tried the vmware patches from the Critical Host patches baseline from vmware and when we install the patch mentioned above, omsa stops working.
Cheers,
Ricardo
radao
7 Posts
0
May 8th, 2014 10:00
Hello Josh,
For now we only tested in R720, however because the installation process is the same and ESXi versions and OMSA installed are the same, we might seem that problem in R710, R720 and R820 also.
For the troubleshoot and things that we tested it doesn't seem to be an "hardware dependent" problem, it seems more some incompatibility between the ESXi 5.1 referenced patch and the OMSA package.
We have the suspicion that could be related to same libs or shared libs changed in the ESX patch.
Thank you,
Please let us know if we can give further info to help.
Ricardo
DELL-Josh Cr
Moderator
Moderator
•
8.5K Posts
0
May 8th, 2014 10:00
Did you try and reboot the server after reinstalling OMSA? We are trying to recreate the issue in our lab.
radao
7 Posts
0
May 8th, 2014 10:00
Hello Josh,
To replicate the problem just install an ESXi 5.1 and update it to the last possible level available from vmware, when ESXi510-201404401-BG patch gets installed omsa stop responding.
We have OMSA openmanage server 7.4 installed in a windows box.
when loggin in the error is "login failed", but the authentication it would be correct, because it was working before the patch installation.
Cheers,
Ricardo
DELL-Josh Cr
Moderator
Moderator
•
8.5K Posts
0
May 8th, 2014 16:00
It looks like it is an issue with this patch and we recommend downgrading to ESXi510-201402001 (build 1612806) until vmware can release a fix.
mdrst32
1 Message
0
May 12th, 2014 09:00
Having the same issue. Would be nice if Dell can investigate this a bit further and work with Vmware to get it resolved. We also are trying to use the OMSA agents for hardware monitoring.
radao
7 Posts
0
May 12th, 2014 12:00
Hello Josh,
There is already an SR open with Dell Support, after VMware requested Dell to work with us to find a solution for this issue.
From the last update from the Dell Engineer taking care of it, this was already escalated to the OMSA Engineering team.
This was already replicated by the Dell Engineer chasing the SR, by the OMSA product team and now is with Engineering team.
We hope to have a solution for this soon with both teams working on this (Dell and VMware).
Cheers,
Ricardo
DELL-Josh Cr
Moderator
Moderator
•
8.5K Posts
0
May 12th, 2014 12:00
We have it escalated to Vmware, but we have to wait for them to patch it.
ishouldntbehere
1 Message
0
May 13th, 2014 22:00
Thought I was losing my mind today... thanks for working through this with the teams to bring a resolution.
bvig-gd
4 Posts
0
May 14th, 2014 11:00
bvig-gd
4 Posts
0
May 14th, 2014 17:00
rpardini
3 Posts
0
June 6th, 2014 09:00
Just a +1. Installing the ESXi510-201404001 (build 1743533, which contains ESXi510-201404401-BG) together with OM-SrvAdmin-Dell-Web-7.3.0-588_A00.VIB-ESX51i causes this problem. Will try reverting to VMWare update02 + ESXi510-201402001 and see if it fixes it.
It is *very* important for Dell+VMWare to fix this, since it seems the patch that causes breakage is also responsible for patching Heartbleed!
bvig-gd
4 Posts
0
June 6th, 2014 09:00
rpardini
3 Posts
0
June 6th, 2014 10:00
Thanks for the update on 5.5U2. I will try it later and report back.
For now, I tested 5.1 with the following results:
1) I couldn't get OMSA 7.3.x to work with whatever ESXi patch; it seems to be a problem with 7.3 web-interface.
2) I could get OMSA 7.2.0.2 to work only up to ESXi build 1612806. Upgrading to build 1743533 breaks OMSA. Also, upgrading to 1743533 breaks all my direct WSMAN calls, with a double-escaping of XML entities in the n1:ReturnValue.
3) I have not tested OMSA 7.4 (I don't have 7.4 webservers)
So it seems if you want to run on 5.1, use ESXi 1612806 (ESXi510-201402001) and OMSA OM-SrvAdmin-Dell-Web-7.2.0-7022 (7.2.02).