Aria Operations cloud proxy deployment from vRLCM fails at stage 9

Products

• VCF Operations/Automation (formerly VMware Aria Suite)
• VMware vSphere ESXi
• VMware vRealize Suite Lifecycle Manager 8.x

Issue/Introduction

During the deployment of VMware Aria Operations cloud proxies via vRealize Suite Lifecycle Manager (vRSLCM / vRLCM), the process fails to complete. Inspection of the "Request details" execution pane in the vRLCM interface indicates that the deployment task halts specifically at stage #9.

Environment

8.18.x

8.0.x

8.18.x

Cause

Port 443 (TCP) communication is blocked between the vRLCM node and the destination ESXi hosts. vRLCM requires direct HTTPS (port 443) access to the target ESXi hosts or the vCenter Server to securely transfer and deploy the cloud proxy OVA. A failure at this stage indicates a timeout or connection refusal during the OVA deployment phase due to network isolation.

/var/log/vrlcm/vmware_vrlcm.log

YYYY-MM-DDTHH:MM:SS.783Z ERROR vrlcm[1299] [pool-3-thread-22] [c.v.v.l.p.c.v.t.DeployOvfTask]  -- IO Exception occured while uploading files to vCenters datastore. Error : {}
java.net.ConnectException: Connection timed out (Connection timed out)
        at java.base/java.net.PlainSocketImpl.socketConnect(Native Method) ~[?:?]
        at java.base/java.net.AbstractPlainSocketImpl.doConnect(Unknown Source) ~[?:?]
        at java.base/java.net.AbstractPlainSocketImpl.connectToAddress(Unknown Source) ~[?:?]
        at java.base/java.net.AbstractPlainSocketImpl.connect(Unknown Source) ~[?:?]
        at java.base/java.net.SocksSocketImpl.connect(Unknown Source) ~[?:?]
        at java.base/java.net.Socket.connect(Unknown Source) ~[?:?]

Resolution

 

1. Coordinate with the network team to review firewall rules and routing configurations.
   
   
2. Allow port 443 (TCP) traffic between the vRLCM appliance and the management network of the target ESXi hosts.
   
   
3. Validate network connectivity from the vRLCM appliance console using standard utilities (e.g., curl -v telnet://<ESXi_IP>:443).
   
   
4. Once the network path is verified as open, retry the deployment request from the vRLCM user interface.