Loading...
Loading...
Errors encountered during IaaS upgrade appear similar to following:System.Data.Services.Client.DataServiceTransportException: The underlying connection was closed: An unexpected error occurred on a send. ---> System.Net.WebException: The underlying connection was closed: An unexpected error occurred on a send. ---> System.IO.IOException: Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host. ---> System.Net.Sockets.SocketException: An existing connection was forcibly closed by the remote host
Eliminate potential upgrade failures during Infrastructure-as-a-Service component upgrades
During IaaS component upgrade, the Web components require network access to a healthy vRealize Automation appliance, to include over a load balanced connection.
Infrastructure-as-a-service upgrades require access to healthy services running on the vRA appliances. The below checks will confirm that network access is available in a load balanced environment.After upgrade of vRealize Automation appliance(s),Check and Verify the following: Validate Service registration For each appliance in the cluster Open a browser connection to https:<vRAApliianceFQDN>:5480Login with root credentialsEnsure services are all REGISTERED with the exception of IaaS Validate vRealize Automation appliances web services are healthy and available: Ensure VIP-FQDN health checks succeed to component-registry: https://<vRA-LoadBalancerVIP-fqdn>/component-registry/services/status/current?limit=100
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.