YYYY-MM-DDT##:##:##.###Z INFO provisioning [host='provisioning-service-app-123456789' thread='vsphere-io-277' user='' org='' trace='' parent='' span=''] c.v.p.c.m.a.v.r.v.VSphereConnectionPool.getConnection:90 - Found existing connection. connectionProperty:[class VSphereConnectionProperties {
YYYY-MM-DDT##:##:##.###Z ERROR provisioning [host='provisioning-service-app-123456789' thread='vsphere-io-277' user='' org='' trace='' parent='' span=''] c.v.p.c.m.a.v.r.vc.VcSession.lambda$getServiceContent$19:591 - [https://<VC_FQDN>/sdk]: Failed to retrieve service content [com.sun.xml.ws.client.ClientTransportException: HTTP transport error: java.net.SocketTimeoutException: Connect timed out
at com.sun.xml.ws.transport.http.client.HttpClientTransport.getOutput(HttpClientTransport.java:103)
com.vmware.photon.controller.model.adapters.vsphere.remotecallmanager.vc.VcSession.lambda$getServiceContent$19(VcSession.java:589)
Caused by: java.net.SocketTimeoutException: Connect timed out
at java.base/sun.nio.ch.NioSocketImpl.timedFinishConnect(NioSocketImpl.java:551)
at java.base/sun.nio.ch.NioSocketImpl.connect(NioSocketImpl.java:602)
at java.base/java.net.SocksSocketImpl.connect(SocksSocketImpl.java:327)
at java.base/java.net.Socket.connect(Socket.java:633
Aria automation 8.x
The request is processed for provisioning where it goes to find VC connection and finds an existing connection. After a while it follows with a socket exception due temporary infra(network) glitch lead to the stuck deployment
In future versions there will be better error handling so that in case of exception it fails so that internally the VSphereConnectionPool goes to create a new connection instead of getting hung.
Workaround
Cancel and re-submit the deployment request.