OPERATIONAL DEFECT DATABASE
...
...
The deploy.sh fails at the Registering embedded vRO stageIn the /var/log/deploy.sh contains: "curl: (22) The requested URL returned error: 400 Bad RequestFailed to register vRO. Will retry in 45 seconds......curl: (22) The requested URL returned error: 400 Bad RequestMaximum 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]"
The appliance received an IP address from the 172.17.x.x range. This conflicts with the internal to the VRO pod docker0 interface.
Currently there is no resolution.
For every VRA8.1 Appliance in the cluster or on a single standalone appliance: Download the attached fix_vco_docker0.sh.Upload the file to the Appliance.SSH to the Appliance with root credentials.Run this command on the fix_vco_docker0.sh file: chmod a+x fix_vco_docker0.shRun the command with: ./fix_vco_docker0.shClick retry on the Life Cycle Manager. Alternatively, execute the steps in the fix_vco_docker0.sh.
Click on a version to see all relevant bugs
VMware Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.
