This post will not contain the complete configuration steps you have to take to configure the Dell OMEVV plugin in your environment but is focused on an issue we encountered when using a proxy for update/lifecycle manager


We had a issue while configuring Dell OMEVV with Lifecycle manager. The integration of the OMEVV plugin in vCenter was not a problem, but as soon as we tried to select the OMEVV plugin in the vSphere vCenter lifecycle manager we ended up with an infinite loop.


First place to look was the logfile on the vCenter

INFO:HsmServiceLogger:Extracted hostname: $IPOMEVV, port: 443
INFO:HsmServiceLogger:Successfully initiated executor
ERROR:HsmServiceLogger:SSL certificate verify failed: HTTPSConnectionPool(host='$IPOMEVV', port=443): Max retries exceeded with url: /omevv/GatewayService/v1/vsphere-lcm/hw-support/v1/packages (Caused by SSLError(SSLEOFError(8, 'EOF occurred in violation of protocol (_ssl.c:1076)')))., start retrying list_packages for 5 times with interval: 5

But although there seems to be an SSL issue the OMEVV plugin in vCenter is registered normaly and everything in vCenter is visible.

So we downloaded the troubleshooting logs from the Dell OME appliance to see if we can find a lead there;

But no matter in what logfile we looked. It didn’t seem that Lifecycle manager was connecting to OMEVV so it seemed that lifecycle manager didn’t even reach OMEVV to get the baselines. That brought us on the right track.

When we first enable lifecycle/update manager on the cluster we did had some issues because it would try to connect to the host via the proxy which was needed voor downloading updates from VMware. So we set some exclusions for local domains to avoid updatemanager to use the proxy for local but because of the OMEVV plugin connects on IP adres bases Lifecycle manager tries to connect via proxy.


So the solution was to add the OMEVV IP adres to the proxy exclusion list. Be sure to edit the file and save your changes.

# Example: NO_PROXY=", do.main, localhost"
NO_PROXY="localhost,, $IPofOMEVV"

 28L, 861B 

Few tips

Validate that your starting/closing quotes are right, because if you make a mistake the file becomes unreadable for the bash startscript and you won’t be able to login #beentheredonethat. (to fix that you have to boot in single user mode and edit the proxy file so it’s correct again).

The first 2 entries in NO_PROXY are mandatory (Localhost, 127.0.01) so don’t change, but append!

You can (also) work with asterix and complete subnets. For Example.

# Example: NO_PROXY=", do.main, localhost"
NO_PROXY="localhost,, .*.tarantino.local,,"

The original article was posted on:

Related articles

  • Cloud Native
  • Application Navigator
  • Kubernetes Platform
  • Digital Workspace
  • Cloud Infrastructure
  • ITTS (IT Transformation Services)
  • Managed Security Operations
  • Multi-Cloud Platform
  • Backup & Disaster Recovery
Visit our knowledge hub
Visit our knowledge hub
Ruud Harreman Virtualization Consultant

Let's talk!

Knowledge is key for our existence. This knowledge we use for disruptive innovation and changing organizations. Are you ready for change?

"*" indicates required fields

First name*
Last name*