You install the update on the vRealize Automation 7.1, 7.2, or 7.3.x virtual appliance to upgrade vRealize Automationand the IaaS components to 7.4.
Do not close the management console while you install the update.
If you encounter any problems during the upgrade process, see Troubleshooting the vRealize Automation Upgrade.
While upgrading the Management Agent on the IaaS virtual machines, a VMware public certificate is temporarily installed in your Trusted Publishers certificate store. The Management Agent upgrade process uses a PowerShell script that is signed with this certificate. When the upgrade is finished, this certificate is removed from your certificate store.
Verify that you selected a download method and completed the procedure for the method. See Downloading vRealize Automation Appliance Updates.
For all high-availability environments, see Back Up Your Existing vRealize Automation Environment.
For environments with load balancers, verify that you disabled all the redundant nodes and removed the health monitors. For information, see your load balancer documentation.
vRealize Automation appliance
IaaS Manager Service
For environments with load balancers, verify that the traffic is directed only to the primary node.
Verify that the IaaS service hosted in Microsoft Internet Information Services (IIS) is running by performing the following steps:
Start a browser and enter the URL https://webhostname/Repository/Data/MetaModel.svc to verify that the Web Repository is running. If successful, no errors are returned and you see a list of models in XML format.
Log in to the IaaS Website and check that the status recorded in the
Repository.logfile reports OK. The file is located in the VCAC home folder at /Server/Model Manager Web/Logs/Repository.log.Note:
For a distributed IaaS Website, log in to the secondary website, without MMD, and stop Microsoft IIS temporarily. To ensure that the load balancer traffic is only going through the primary Web node, check the MetaModel.svc connectivity, and restart the Microsoft IIS.
Verify that all IaaS nodes are in a healthy state by performing the following steps:
On the primary virtual appliance, log in to vRealize Automation Appliance Management as root using the password you entered when you deployed the vRealize Automation appliance.
Under Last Connected, verify the following.
The IaaS nodes in the table have a last connected time of less than 30 seconds.
The virtual appliance nodes have a last connected time of less than 10 minutes.
If the IaaS nodes are not in communication with the vRealize Automation appliance, the upgrade fails.
To diagnose connectivity problems between the Management Agent and virtual appliance, perform these steps.
Log in to each IaaS node that is not listed or has a Last Connected time greater than 30 seconds.
Check the Management Agent logs to see if any errors are recorded.
If the Management Agent is not running, restart the agent in the Services console.
Note any orphaned nodes listed in the table. An orphaned node is a duplicate node that is reported on the host but does not exist on the host. You must delete all orphaned nodes. For more information, see Delete Orphaned Nodes on vRealize Automation .
If you have a replica virtual appliance that is no longer part of the cluster, you must delete it from the cluster table. If you do not delete this appliance, the upgrade process displays a warning message that the replica update is unsuccessful.
Verify that all saved and in-progress requests have finished successfully before you upgrade.
If you upgrade the IaaS components manually after you update the vRealize Automation 7.1, 7.2, or 7.3.x appliance, see Exclude IaaS Upgrade. If you plan to upgrade IaaS manually, you must also stop all IaaS services, except Management Agent, on each IaaS node.
- On your primary vRealize Automation appliance, log in to vRealize Automation Appliance Management as root using the password you entered when you deployed the vRealize Automation appliance.
For a distributed environment, open the management console on the master appliance.
- Click Services and verify that all services are registered.
- Select vRealize Automation appliance.
and verify that this appliance is the master
You install the update only on the master vRealize Automation appliance. Each replica vRealize Automation appliance is updated with the master appliance.
- Select .
- Click Check Updates to verify that an update is accessible.
- (Optional) For instances of vRealize Automation appliance, click Details in the Appliance Version area to see information about the location of release notes.
- Click Install Updates.
- Click OK.
A message stating that the update is in progress appears. The system shows changes made during an upgrade on the Update Summary page. The time required for the update to finish varies according to your environment and network.
- (Optional) To monitor the update in greater detail, use a terminal emulator to log in to the primary appliance. View the updatecli.log file at /opt/vmware/var/log/vami/updatecli.log.
Additional upgrade progress information can also be seen in these files.
If you log out during the upgrade process, you can continue to follow the update progress in the log file. The updatecli.log file might display information about the version of vRealize Automation that you are upgrading from. This displayed version changes to the proper version later in the upgrade process.
- When the vRealize Automation appliance update finishes, click in the management console.
In a distributed environment, all successfully upgraded replica appliance nodes reboot when you reboot the master appliance.
The IaaS update starts when the system is initialized and all services are up and running. Clickto observe the IaaS upgrade progress.
- When the IaaS update finishes, click Cluster in the appliance management console and verify that the version number is the current version for all IaaS nodes and components.
- Click the Telemetry in the appliance management console. Read the note about participation in the Customer Experience Improvement Program (CEIP) and select to join or not join the program.
Details regarding the data collected through CEIP and the purposes for which it is used by VMware are set forth at the Trust & Assurance Center at http://www.vmware.com/trustvmware/ceip.html.
For more information about the Customer Experience Improvement Program, see Join or Leave the Customer Experience Improvement Program for vRealize Automation.
What to do next
If your deployment uses a load balancer, perform these steps.
Enable the load balancer vRealize Automation health checks.
Re-enable the load balancer traffic for all vRealize Automation nodes.
If the IaaS components fail to upgrade, see Upgrading the IaaS Server Components Separately If the Update Process Fails.