During software provisioning, the provisioned VM tries to communicate directly with one of the vRA node's IP addresses rather than the LB address

Products

• VMware Aria Suite

Issue/Introduction

Symptoms:

During software provisioning, the provisioned virtual machine tries to communicate directly with one of the vRealize Automation node's IP addresses rather than the virtual IP load balancing address.

Environment

VMware vRealize Automation 7.x

Cause

• The Software Service facilitates communications between virtual machines and the virtual appliance.  Due to the virtual appliances running in High Availability (HA) mode in 2 node or a 3 node configurations, there are certain configuration changes that need to happen to ensure that the software agents and the agent bootstrap are routed via the Load Balancer (LB) rather than the individual nodes. There may or may not be connectivity to the individual vRealize Automation nodes from the deployed virtual machine provisioning software.
• Once the HA mode is deployed, create specific custom properties which will change the means in which the software provisioning will be routed via the load balancer. You can choose to add the custom properties at the reservation level, endpoint level or even at the blueprint level. Endpoint level additions will be most optimal as once added at an endpoint, all blueprints deployed under that reservation/endpoint would automatically be HA compliant for software provisioning. If specified at a blueprint level all blueprints will need the custom properties specified.

Resolution

This issue is resolved in vRealize Automation 7.6.

Workaround:

• Use these Custom properties applied to one of the previous discussed consumption levels (recommendation to apply at endpoint level):

software.agent.service.url = https://VRA-LB-FQDN/software-service/api
software.ebs.url = https://VRA-LB-FQDN/event-broker-service/api
agent.download.url = https://VRA-LB-FQDN/software-service/resources/nobel-agent.jar