Unsolved
This post is more than 5 years old
2 Posts
0
3337
December 4th, 2017 09:00
OMIVV - Proactive HA breaks vCenter Appliance
Activating the Proactive HA provider supplied by OMIVV (4.1) on the VMware vCenter Appliance (6.5.0.12000) results in the vCenter services being unable to start on subsequent reboots of the VCSA. Tested with a brand new deployment of both VCSA and the OMIVV appliances. Anyone else see this behavior?
No Events found!
DELL-Vijay B
183 Posts
0
December 5th, 2017 05:00
Hi,
We have come across about one such instance but unfortunately could not simulate the same in our environment.
We will recommend to get in touch with Dell TechSupport so that they can take a closer look and gather necessary logs for the team to identify the problem whether on VC or OMIVV plugin side.
Thanks,
Vijay
cstevens42
2 Posts
0
December 6th, 2017 08:00
VMware Support tells me this is actually a known issue internally (i.e., no public KB article). The problem is that registering the Proactive HA provider is supposed to write the Dell provider ID in a couple of tables in the vCenter database, but it does not. This results in errors starting the vCenter service. The workaround is to have VMware Support manually update the database after activating Proactive HA with the Dell provider.
What I want to know is what is Dell doing to fix this? A bug that renders the vCenter Appliance unusable is a big bug indeed. OMIVV 4.1 was released in August; surely enough time has passed to identify and fix the issue.