7.4
Table Of Contents
- Upgrading from vRealize Automation 7.1 or Later to 7.4
- Contents
- Upgrading vRealize Automation 7.1, 7.2, or 7.3.x to 7.4
- Upgrading VMware Products Integrated with vRealize Automation
- Preparing to Upgrade vRealize Automation
- Run NSX Network and Security Inventory Data Collection Before You Upgrade vRealize Automation
- Backup Prerequisites for Upgrading vRealize Automation
- Back Up Your Existing vRealize Automation Environment
- Set the vRealize Automation PostgreSQL Replication Mode to Asynchronous
- Downloading vRealize Automation Appliance Updates
- Updating the vRealize Automation Appliance and IaaS Components
- Upgrading the IaaS Server Components Separately If the Update Process Fails
- Upgrading vRealize Orchestrator After Upgrading vRealize Automation
- Enable Your Load Balancers
- Post-Upgrade Tasks for Upgrading vRealize Automation
- Upgrading Software Agents to TLS 1.2
- Set the vRealize Automation PostgreSQL Replication Mode to Synchronous
- Run Test Connection and Verify Upgraded Endpoints
- Run NSX Network and Security Inventory Data Collection After You Upgrade from vRealize Automation
- Join Replica Appliance to Cluster
- Port Configuration for High-Availability Deployments
- Reconfigure Built-In vRealize Orchestrator for High Availability
- Restore External Workflow Timeout Files
- Enabling the Connect to Remote Console Action for Consumers
- Restore Changes to Logging in the app.config File
- Enable Automatic Manager Service Failover After Upgrade
- Troubleshooting the vRealize Automation Upgrade
- Automatic Manager Service Failover Does Not Activate
- Installation or Upgrade Fails with a Load Balancer Timeout Error
- Upgrade Fails for IaaS Website Component
- Manager Service Fails to Run Due to SSL Validation Errors During Runtime
- Log In Fails After Upgrade
- Delete Orphaned Nodes on vRealize Automation
- Join Cluster Command Appears to Fail After Upgrading a High-Availability Environment
- PostgreSQL Database Upgrade Merge Does Not Succeed
- Replica vRealize Automation Appliance Fails to Update
- Backup Copies of .xml Files Cause the System to Time Out
- Exclude Management Agents from Upgrade
- Unable to Create New Directory in vRealize Automation
- vRealize Automation Replica Virtual Appliance Update Times Out
- Some Virtual Machines Do Not Have a Deployment Created During Upgrade
- Certificate Not Trusted Error
- Installing or Upgrading to vRealize Automation Fails
- Unable to Update DEM and DEO Components
- Update Fails to Upgrade the Management Agent
- Management Agent Upgrade is Unsuccessful
- vRealize Automation Update Fails Because of Default Timeout Settings
- Upgrading IaaS in a High Availability Environment Fails
- Work Around Upgrade Problems
n
Work Around Upgrade Problems
Automatic Manager Service Failover Does Not Activate
Suggestions for troubleshooting manager-service-automatic-failover command.
Solution
n
The manager-service-automatic-failover command fails or displays this message for more than two
minutes: Enabling Manager Service automatic failover mode on node:
IAAS_MANAGER_SERVICE_NODEID.
a Log in to vRealize Automation appliance management at https://va-hostname.domain.name:5480
with the user name host and the password you entered when you deployed the appliance.
b Select vRA Settings > Cluster.
c Verify that the Management Agent service is running on all Manager Service hosts.
d Verify that the last connected time for all IaaS Manager Service nodes is less than 30 seconds.
If you find any Management Agent connectivity issues, resolve them manually and retry the command
to enable the Manager Service automatic failover.
n
The manager-service-automatic-failover command fails to enable failover on a Manager Service
node. It is safe to rerun the command to fix this.
n
Some Manager Service hosts in the IaaS deployment have failover enabled while other hosts do not.
All Manager Service hosts in the IaaS deployment must have the feature enabled or it does not work.
To correct this issue, do one of the following:
n
Disable failover on all Manager Service nodes and use the manual failover approach instead.
Only run failover on one host at a time.
n
If multiple attempts fail to enable the feature on a Manager Service node, stop the Windows
VMware vCloud Automation Center Service on this node and set the node startup type to Manual
until you resolve the issue.
n
Use Python to validate that failover is enabled on each Manager Service node.
a Log in to the master vRealize Automation appliance node as root using SSH.
b Run python /usr/lib/vcac/tools/vami/commands/manager-service-automatic-
failover ENABLE.
c Verify that the system returns this message: Enabling Manager Service automatic
failover mode on node: IAAS_MANAGER_SERVICE_NODEID done.
n
Validate that failover is enabled on each Manager Service node by inspecting the Manager Service
configuration file.
a Open a command prompt on a Manager Service node.
b Navigate to the vRealize Automation installation folder and open the Manager Service
configuration file at VMware\vCAC\Server\ManagerService.exe.config.
Upgrading from vRealize Automation 7.1 or Later to 7.4
VMware, Inc. 61