This article contains a list of known issues that are resolved in the latest patch available for vRealize Automation 7.5
Current Patch Version:  Patch 27
List of issues resolved in this patch:

See the attached spreadsheet titled:  vRA75-P27-ResolvedList.xlsx for a full list of all resolved issues and their associated Symptom(s).  A download link is also available under the File(s) / Attachment(s) section of this KB.

To resolve the listed issues, install the latest vRealize Automation 7.5 patch with the instructions below.

Note:  If you wish to deploy this patch using vRealize Suite Lifecycle Manager, you will need to use the properly "wrapped" patch file and not the one listed within this article.  To obtain the wrapped patch for vRealize Automation, follow the instructions here:  How to Download vRealize Suite product patches in Customer Connect

Prerequisites

• If Database tab within the 5480 VAMI clustering is set to SYNC, convert to ASYNC
• Ensure that the virtual appliance(s) have their timezone set to UTC
• Remove old / obsolete nodes from the Distributed Deployment Information Table. For detailed steps, see Remove a Node from the Distributed Deployment Information Table section of vRealize Automation documentation.
• Ensure that VMware vCloud Automation Center Management Agent is the latest 7.5 version and is running on all IaaS cluster nodes.
• Ensure 16GB of freespace is available for each virtual appliance participating in the cluster for the /dev/sdd1 partition.
• Ensure at least 1024 MB free on 'C:\' for each IaaS node.
• VMware vCloud Automation Center Management Agent service account requirements:
  • Ensure "Log on as a service account" is enabled. 
  • Local Administrator
  • Required username format should be in down-level domain format: domain\username, e.g. "vra\administrator".
• On each vRA Virtual Appliance nodes, open the /etc/hosts file and locate the entry IPv4 loopback IP Address (127.0.0.1). Ensure that the Fully Qualified Domain Name of the node is added immediately after 127.0.0.1 and before localhost.

• Verify that you have taken a snapshot of the vRealize Automation system while it is shut down. This is the preferred method of taking a snapshot. See the recommendation below:

  Shutdown and Startup Order for Snapshots:

  Shutdown	Startup
  Proxy Agents	Primary appliance
  Distributed Execution Managers	Secondary appliance
  Secondary Manager service	Primary Web node
  Primary Manager Services	Secondary Web node
  Secondary Web node	Primary MS
  Primary Web node	Secondary MS
  Secondary appliances	Distributed Execution Managers
  Primary appliance	Agents

   
• If your environment uses load balancers for high availability, disable traffic to secondary nodes and disable service monitoring until after installing or removing patches and all services are showing REGISTERED. 
• Obtain the files from below and copy it to the file system available to the browser you use for the vRealize Automation appliance management interface.

Note!  If you attempt to install or remove a patch without all nodes running, the vRealize Automation appliance management interface might become unresponsive. If that happens, contact technical support. Do not attempt to manage patches through other means or use vRealize Automation until you resolve the issue.

Installation Procedure

All Patch downloads have moved to Customer Connect.

1. Download the file from the above link and verify the checksum.
2. Log in to the vRealize Automation appliance management interface (https://vrealize-automation-appliance-FQDN:5480) as root.
3. Upload the patch by clicking  vRA Settings > Patches > Patch Management > New Patch > Upload
4. After the patch uploads successfully, log out of the current browser session.
5. If the previously applied patch version is lower than Patch 9, then perform the below steps, else move to step #6:
   1. SSH into the primary virtual appliance that the file was just uploaded to.
   2. Execute this command:  

      sh /usr/lib/vcac/patches/repo/contents/vRA-patch/patchscript.sh

   3. Wait for the command to complete.
   4. If it throws an error, fix the error and re-run Step #5.2
6. Clear browser cache and login to the primary node appliance management interface again.
7. Navigate to vRA Settings > Patches > Patch Management > New Patch
8. A new pre-check box appears.  Click Run Pre-check and wait for it to complete
9. Once the pre-checker is green, click Install
10. Select Done
11. Once the installation is complete and successful, ensure all the services are running.

Verification of successful patch installation

• The Installed Patches tab shows a successful installation

curl -k -X GET --header 'Accept: text/plain' --header 'Authorization: Basic randomtokenID' 'https://vRAFQDN:5480/config/patch-last-applied-patch' 

Adding new nodes to an existing patched vRealize Automation environment

1. Keep the environment in Async replication mode.
2. Deploy a fresh appliance for the environment, click on Cancel when the Installation wizard pops after logging into the 5480 appliance management interface page.
3. Re-join the new node to the primary from the Cluster tab
4. From the Patch tab on the appliance management page of the primary node, re-initiate the installation of the patch.

service horizon-workspace start
Note: Wait until the service is started and then execute the next command.