Two embedded vRO endpoints exists in vRA 8.4 after a new vRA load balancer is configured

Products

• VMware Aria Suite

Issue/Introduction

Symptoms:
The embedded vRO was renamed from "embedded-VRO" before the new load balancer configuration. After the LB configuration is completed there are two embedded vRO integrations.

Environment

VMware vRealize Orchestrator 8.x
VMware vRealize Automation 8.4.x

Cause

The embedded vRO registration in vRA 8.4 will fail to update the embedded vRO endpoint if new vRA LB is configured.
The vRO registration code in vRA 8.4 (/opt/scripts/register_vro_endpoint.sh) is modified to search for the previous embedded vRO endpoint, using the following criteria:

single node: host = LB or host = node1
cluster: host = LB or host = node1 or host = node2 or host = node3

Introducing new LB value will cause the above search to fail and vRA 8.4 deployment will create a new embedded vRO endpoint registration with the name “embedded-VRO”.
After the vRA deployment there will be two embedded vRO registrations - the existing one, which won’t be updated and the URL will point to the old load balancer URL (https://{old LB host}:443) and a new one with the name “embedded-VRO” created from the deploy.sh script.

Resolution

1. Change the embedded vRO registration code (/opt/scripts/register_vro_endpoint.sh) in vRA 8.4 available in attachment section in this article. The vRO registration code must be changed in all of the vRA nodes.
   1. Rename the existing vRO registration code with:

> mv /opt/scripts/register_vro_endpoint.sh /opt/scripts/register_vro_endpoint.sh.bak

2. Copy the new vRO registration code from attachment in the /opt/scripts folder of the vRA appliance.
3. Edit the file permissions of the new vRO registration code with:

chmod 700 /opt/scripts/register_vro_endpoint.sh

4. check the file permissions with:

ls -la /opt/scripts/register_vro_endpoint.sh

5. the command result should be similar to:

-rwx------ 1 root root 2737 Apr 19 13:28 /opt/scripts/register_vro_endpoint.sh

 

2. Delete the newly created embedded vRO integration with URL pointing to the new LB from the UI
   1. Login in vRA UI -> Go to Cloud Assembly -> Infrastructure Tab -> Integrations.

 {vRA FQDN}/automation-ui/#/provisioning-ui;ash=%2Fintegrations

2. Open the embedded vRO integration with the name “embedded-VRO” and make sure that the vRealize Orchestrator URL is pointing to the new LB host - https://{new LB host}:443
3. Delete this wrongly created vRO integration.

3. Change existing vRO integration properties - vRealize Orchestrator URL and rename the existing embedded vRO to “embedded-VRO” from the UI {vRA FQDN}/automation-ui/#/provisioning-ui;ash=%2Fintegrations.
   1. Login in vRA UI > Go to Cloud Assembly > Infrastructure Tab > Integrations.
   2. Open the embedded vRO integration, rename it to “embedded-VRO” and change the vRealize Orchestrator URL to https://{new LB host}:443
   3. Click the validate button and ensure that the endpoint validation is successful, ignoring all of the UI's failed data collection errors.
   4. Click Save.
4. After those steps, run /opt/scripts/deploy.sh again. The vRA deployment code should pass successfully and there should be only one embedded vRO integration.