While initiating the Inventory Sync for VMware Identity Manager from VMware Aria Suite Lifecycle Manager (vRSLCM), the operation fails with the following error message:
The following error was captured in the /var/log/vrlcm/vmware_vrlcm.log:
ERROR vrlcm[1109] [pool-3-thread-41] [c.v.v.l.u.SessionHolder] -- SessionHolder.newSession Exception encountered com.jcraft.jsch.JSchException: timeout: socket is not established at com.jcraft.jsch.Util.createSocket(Util.java:418) ~[jsch-0.2.13.jar!/:0.2.13] at com.jcraft.jsch.Session.connect(Session.java:219) ~[jsch-0.2.13.jar!/:0.2.13] at com.vmware.vrealize.lcm.util.SessionHolder.newSession(SessionHolder.java:53) [lcm-util-8.18.0-SNAPSHOT.jar!/:?] at com.vmware.vrealize.lcm.util.SessionHolder.<init>(SessionHolder.java:37) [lcm-util-8.18.0-SNAPSHOT.jar!/:?] at com.vmware.vrealize.lcm.util.SshUtils.executeWithKnownTimeout(SshUtils.java:747) [lcm-util-8.18.0-SNAPSHOT.jar!/:?] at com.vmware.vrealize.lcm.util.SshUtils.runCommandWithKnownTimeout(SshUtils.java:581) [lcm-util-8.18.0-SNAPSHOT.jar!/:?] at com.vmware.vrealize.lcm.vidm.driver.helpers.VidmUtil.runVidmSshCommand(VidmUtil.java:196) [vmlcm-vidmplugin-driver-8.18.0-SNAPSHOT.jar!/:?] at com.vmware.vrealize.lcm.vidm.clustering.util.VidmPgpoolUtil.getStatus(VidmPgpoolUtil.java:1176) [vmlcm-vidmplugin-driver-8.18.0-SNAPSHOT.jar!/:?] at com.vmware.vrealize.lcm.vidm.core.task.VidmClusterUpdateNodeTypesTask.execute(VidmClusterUpdateNodeTypesTask.java:124) [vmlcm-vidmplugin-core-8.18.0-SNAPSHOT.jar!/:?] at com.vmware.vrealize.lcm.automata.core.TaskThread.run(TaskThread.java:62) [vmlcm-engineservice-core-8.18.0-SNAPSHOT.jar!/:?] at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:?] at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:?]
The issue is caused by a failure in SSH communication between Aria Lifecycle Manager and VMware Identity Manager. This may result in the hostname resolution or retrieval logic returning null or empty, leading to the error.
To resolve the issue:
Incase, SSH connectivity from LCM to vIDM nodes succeeds via shortname/IP but fails via FQDN, follow the below steps:
1. SSH to vRLCM.
2. Update "/etc/hosts" file of vRLCM server with below entries.
# Begin /etc/hosts (network card version) # End /etc/hosts (network card version) # VAMI_EDIT_BEGIN # Generated by Studio VAMI service. Do not modify manually. 127.0.0.1 usdc1-vrslcm.pbi.global.pvt usdc1-vrslcm localhost vIDM-Node1-IP vIDM-Node1-FQDN vIDM-Node1-ShortName vIDM-Node2-IP vIDM-Node2-FQDN vIDM-Node2-ShortName vIDM-Node3-IP vIDM-Node3-FQDN vIDM-Node3-ShortName ::1 usdc1-vrslcm.pbi.global.pvt usdc1-vrslcm localhost ipv6-localhost ipv6-loopback # VAMI_EDIT_END
3. Retry Inventory Sync from Aria Lifecycle Manager.