VMware Aria Orchestrator fails to register post upgrade when deploy.sh is run if the endpoint was renamed

Products

• VCF Operations/Automation (formerly VMware Aria Suite)

Issue/Introduction

• Deploy.sh fails at the "Registering embedded vRO" stage
• Within the /var/log/deploy.sh file you see entries similar to the following:
  curl: (22) The requested URL returned error: 400 Bad Request
Failed to register vRO. Will retry in 45 seconds...
…
curl: (22) The requested URL returned error: 400 Bad Request
Maximum number of retries exceeded.
• The provisioning-service log file contains entries similar to the following:
  2021-03-01T09:42:37.536Z WARN provisioning [host='provisioning-service-app-xxxxxxxxxx-xxxxx' thread='xn-index-queries->27' user='provisioning-xxxxxxxxxxxxxxxx' org='xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx' trace='xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx' parent='xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx' span='xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx'] >c.v.p.c.m.t.EndpointAllocationTaskService.log:453 - [8282/provisioning/endpoint-tasks/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx] Referrer null is patching us to failure during subStage CHECK_IF_ACCOUNT_EXISTS: {
"message": "Endpoint configuration (link: /resources/endpoints/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx) (resource: >) already exists for organization xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx and data collector https://VRAFQDN:443.","messageId": "0",
"stackTrace": ["com.vmware.automation.vro.gateway.services.VroEndpointAdapterServiceImpl.lambda$handleAccountExists$11(VroEndpointAdapt>erServiceImpl.java:187)",

Environment

VMware Aria Automation 8.x

Cause

The embedded-vRO endpoint was renamed.

Resolution

Workaround:

1. Rename the embedded vRO endpoint back to "embedded-VRO"
2. Redeploy services using /opt/scripts/deploy.sh or using VMware Aria Suite Lifecycle 8.x