vjrk83
Contributor
Contributor

Life Cycle manager fails to connect to depot after upgrade to 7.0u3c ( for images only)

Upgraded to latest version 7.0u3 and image compliance is successfull, but the Life cycle manager fails to connect to depot. The error is An error occurred while connecting to depot. ( attached screenshot also) 

Whereas if I create a new cluster and move hosts to use Baseline , that works. So something is not correct may be default port changed to some custom port. Would someone please able to help ? Thanks. 

 

 

0 Kudos
8 Replies
RealQuiet
Enthusiast
Enthusiast

Did you check your proxy settings? Make sure they are not cleared out and/or that you have the correct entries for when it should bypass the proxy. 

 

/etc/sysconfig/proxy

 

NO_PROXY="localhost, 127.0.0.1,<vcsa_fqdn>, <vcsa_ip>,<sddc_fqdn>,<sddc_ip> "

0 Kudos
vjrk83
Contributor
Contributor

Its just the default. We dont have any proxy. 

 

# Enable a generation of the proxy settings to the profile.
# This setting allows to turn the proxy on and off while
# preserving the particular proxy setup.
#
PROXY_ENABLED="no"

# Some programs (e.g. wget) support proxies, if set in
# the environment.
# Example: HTTP_PROXY="http://proxy.provider.de:3128/"
HTTP_PROXY=""

# Example: HTTPS_PROXY="https://proxy.provider.de:3128/"
HTTPS_PROXY=""

# Example: FTP_PROXY="http://proxy.provider.de:3128/"
FTP_PROXY=""

# Example: GOPHER_PROXY="http://proxy.provider.de:3128/"
GOPHER_PROXY=""

# Example: SOCKS_PROXY="socks://proxy.example.com:8080"
SOCKS_PROXY=""

# Example: SOCKS5_SERVER="office-proxy.example.com:8881"
SOCKS5_SERVER=""

# Example: NO_PROXY="www.me.de, do.main, localhost"
NO_PROXY="localhost, 127.0.0.1"

0 Kudos
baijup
VMware Employee
VMware Employee

@vjrk83 Can you please check following logs at the same time of the error "An error occurred while connecting to depot." shown  on compliance check screen.

On VC:
/var/log/vmware/vmware-updatemgr/vum-server/vmware-vum-server.log

On ESXi Host which was selected for Compliance Check:
/var/run/log/lifecycle.log

Following are some keywords which will show in the logs:

DepotConnectError
Unable to connect

If feasible please share these logs or specific error snippets to identify the reason for connection failure error.

Thanks,

0 Kudos
vjrk83
Contributor
Contributor

Thanks, I think I found the issue. Our VCSA has two networks with different vlan and DNS, the Depot is trying to use the other interface which connection times out. (screenshot attached). 


I think the FQDN name for LifeCycle Manager needs to be updated. Do you know how to update that ? In older versions, Update manager had a very easy way to change the FQDN, Life Cycle manager doesnt have that feature. 

Tags (1)
0 Kudos
vjrk83
Contributor
Contributor

 
0 Kudos
vjrk83
Contributor
Contributor

Anyone has a KB to update the LifeCycle Manager FQDN ?  Looking for a similar option that was there on VMware 6.7 (update manager ) 

https://docs.vmware.com/en/VMware-vSphere/6.7/com.vmware.vsphere.update_manager.doc/GUID-997B7FFB-24... 

 

0 Kudos
baijup
VMware Employee
VMware Employee

@vjrk83 I will check the steps and circle back, ideally LifeCycle Manager will use the PNID (FQDN) during deployment, if it is not taking PNID, we will have to verify the locations with the old name. Can you verify the url in file /usr/lib/vmware-updatemgr/bin/extension.xml ?

0 Kudos
anonymous_geek
Contributor
Contributor

Our problem was  firewall port tcp 9084 closed out to host 2

0 Kudos