VRA/VRO deployment of version 8.1 or upgrade to version 8.1 fails when the appliance is deployed in a 172.17.x.x network

Products

• VMware Aria Suite

Issue/Introduction

Symptoms:

• The deploy.sh fails at the Registering embedded vRO stage
• In the /var/log/deploy.sh contains:

"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 tango-vro-gateway log file contains:

"2020-04-16T02:12:22.820Z [priority='ERROR' thread='reactor-http-epoll-1' user='' org='' context='' parent='' token=''] c.v.a.v.g.c.ControllerExceptionHandler.handleVroServiceException:62 - 920001: Bad credentials.
 com.vmware.automation.vro.exceptions.VroServiceException: 920001: Bad credentials.
  at com.vmware.automation.vro.exceptions.Errors.createServiceException(Errors.java:25)
  Suppressed: reactor.core.publisher.FluxOnAssembly$OnAssemblyException: 
 Error has been observed at the following site(s):
  |_ checkpoint ⇢ Handler com.vmware.automation.vro.gateway.controllers.EndpointConfigurationAdapterController#configureEndpoint(EndpointConfigurationRequest) [DispatcherHandler]"

Environment

VMware vRealize Automation 8.1.x

Cause

The appliance received an IP address from the 172.17.x.x range. This conflicts with the internal to the VRO pod docker0 interface.

Resolution

Currently there is no resolution.

Workaround:
For every VRA8.1 Appliance in the cluster or on a single standalone appliance:

1.  Download the attached fix_vco_docker0.sh.
2. Upload the file to the Appliance.
3. SSH to the Appliance with root credentials.
4. Run this command on the fix_vco_docker0.sh file: chmod a+x fix_vco_docker0.sh
5. Run the command with: ./fix_vco_docker0.sh
6. Click retry on the Life Cycle Manager.

Alternatively, execute the steps in the fix_vco_docker0.sh.