You install the VMware vRealize ™ Automation 7.2 update on the vRealize Automation 7.0 or 7.0.1 appliance and configure appliance settings.

About this task

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.

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 7.0 or 7.0.1 Upgrade.

Note:

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.

Prerequisites

  • Verify that you selected a download method and downloaded the update. See Downloading vRealize Automation Appliance Updates.

  • For all high-availability environments, see Back Up Your Existing vRealize Automation 7.0 or 7.0.1 Environment.

  • For high-availability environments with load balancers, verify that you disabled all of the redundant nodes and removed the health monitors for these items according to your load balancer documentation.

    • vRealize Automation appliance

    • IaaS Website

    • IaaS Manager Service

  • For high-availability 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:

    1. 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.

    2. Log in to the Web node of the IaaS virtual machine and check that the status recorded in the Repository.log file 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. Check the MetaModel.svc connectivity to verify that the load balancer traffic is only going through the primary Web node, and restart the Microsoft IIS.

  • If you have a Common Components Catalog component installed in your environment, uninstall the component before you upgrade. For information, see the Common Components Catalog Installation Guide..

  • Verify that all IaaS nodes are in a healthy state by performing the following steps:

    1. Go to the management console for your primary virtual appliance by using its fully qualified domain name, https://va-hostname.domain.name:5480.

    2. Log in with the user name root and the password you specified when the appliance was deployed.

    3. Select vRA settings > Cluster.

    4. Under Last Connected in the table, verify that the IaaS nodes have a last connected time of less than 3 minutes and that the virtual appliance nodes have last connected time of less than 10 minutes.

      If all the IaaS nodes are not in communication with the vRealize Automation appliance, the upgrade fails.

      To diagnose connectivity issues between the Management Agent and virtual appliance, log in to the IaaS node that has a last connected time of more than 3 minutes and check the Management Agent logs. Go to the Services console. If the Management Agent status shows that it is not running, restart the Management Agent .

    5. 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.

  • Verify that all saved and in-progress requests have finished successfully before you upgrade.

  • If you plan to use the IaaS shell upgrade script to upgrade the IaaS components after you update the vRealize Automation 7.0 or 7.0.1 appliance, see Exclude Management Agents from Upgrade.

Procedure

  1. Open the vRealize Automation appliance management console.
    1. Go to the management console for your virtual appliance by using its fully qualified domain name, https://va-hostname.domain.name:5480.
    2. Log in with the user name root and the password you specified when the appliance was deployed.
  2. Click Services and verify that all services are REGISTERED.
  3. If the PostgreSQL database is embedded, select vRA Settings > Database to verify that this is the master or primary vRealize Automation appliance.
  4. Select Update > Status.
  5. Click Check Updates to verify that an update is accessible.
  6. (Optional) : For instances of vRealize Automation appliance, click Details in the Appliance Version area to see information about the location of release notes.
  7. Click Install Updates.
  8. Click OK.

    A message stating that the update is in progress appears.

  9. (Optional) If you have not resized Disk 1 to 50 GB manually, complete the following steps:
    1. When the system prompts you to reboot the virtual appliance, click the System tab and click Reboot.

      During the reboot, the system adjusts the space required for the update.

    2. After the system reboots, log in again to the vRealize Automation appliance management console and verify that each service, except iaas-service, is listed as REGISTERED. Select Update > Status.
    3. Click Check Updates and Install Updates.
  10. To monitor the upgrade progress, use a terminal emulator to log in to the master appliance node and view the updatecli.log file at /opt/vmware/var/log/vami/updatecli.log.

    Additional upgrade progress information can also be seen in these files.

    • /opt/vmware/var/log/vami/vami.log

    • /var/log/vmware/horizon/horizon.log

    • /var/log/bootstrap/*.log

    If you log out during the upgrade process and log in again before the upgrade is finished, you can continue to follow the progress of the update 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.

    The time required for the update to finish varies according to your environment and network.

  11. After the update finishes, reboot the primary appliance.
  12. Verify that each service, except iaas-service, is running.
    1. Log in to the vRealize Automation appliance management console.
    2. Click Services.
    3. Click Refresh to monitor the service startup progress.

      You should see a minimum of 35 services.

    4. Verify that each service, except iaas-service, is listed as REGISTERED.

      The release-management service does not start without a vRealize Code Stream license key.

  13. Read the note about participation in the Customer Experience Improvement Program and select to join or not join the program.

    For information about the program, click the Telemetry tab in the appliance management console.

    For more information about setting parameters for data collection and joining or leaving the Customer Experience Improvement Program after you have upgraded, see Join or Leave the Customer Experience Improvement Program for vRealize Automation.

What to do next