VMware vRealize Automation 7.6 – Patch 14 Released

It seems like it wasn’t too long ago that I posted that Patch 3 had been released for vRealize Automation 7.6 (technically it was March 2, 2020). Since then, VMware has been quite busy resolving various issues within vRealize Automation 7.6 and have released 11 additional patches as well as 2 cumulative security updates. Patch 14 for vRealize Automation 7.6 was released by VMware on September 22, 2020, and only contains 1 fix related to “Email notifications fail to work properly over time requiring service restarts”.

Since I last posted about Patch 3, below is the full list of issues resolved since Patch 3:

• Patch 4
  • vRO custom validation does not work in vRA XaaS blueprint - validation message does not appear
  • Request returns an error in directory URL
  • The description field retains default value, regression from vRA 7.5 behavior.
  • After a number of months, audit.log could fill disk space
  • The infrastructure tab is not accessible on the vRA UI.  404 error.  On VAMI shell-ui-app shows as FAILED
• Patch 5
  • Open deployment, navigate to Request History, review log component, text area and text within should not be visible
  • The default read/write timeout is 10 seconds within the HTTP client used by NSX-T SDK
  • Hardening introduced by Microsoft: https://support.microsoft.com/en-ca/help/4520412/2020-ldap-channel-binding-and-ldap-signing-requirement-for-windows
• Patch 6
  • Reconfigure requests fail with misleading information regarding the submitted action
  • Day 2 operation to reconfigure a managed machine removes networking properties
  • Addresses licensing issues
• Patch 7
  • The label of the network in returned from API reservation JSON is the old network name
  • Resubmit of a failed deployment using custom forms will not allow a value to be selected from the multi-value picker
  • When using an external action and a constant value in the MultiValue Picker in a custom form, the constant value gets dropped from the form after the External actions load.
• Patch 8
  • Add support for VirtualMachine.Admin.ThinProvision and VirtualMachine.Admin.EagerZero custom properties
• Patch 9
  • .tmp files from Management Agents are filling up /tmp directory
  • Performance issue on Catalog and Postgres - java.net.SocketTimeoutException I/O error
  • Unable to load resource with id xxxxxxxxxxxxxxxxx from ServiceCatalog
• Patch 10
  • Deployment listed and search under deployment tabs are showing inconsistent data.
  • Fatal: Unable to update database error message is displayed on the vRA appliance console after a Disaster Recovery of vRA
  • Unable to Power On virtual machines after upgrading vRA, fails with error “One or more errors occurred”
  • Error 400 when requesting XaaS Day2 Action on Dynamic Type via API
  • Wrong port group assignment for link cloned machines
  • Oracle backed Directory configurations are not synchronizing
  • Custom forms missing data grid object and values on resubmissions
  • Deployment with NSX-T LB can fail to destroy
  • Custom Forms - Binding “Request Info” not available after vRA 7.6 P7 is applied
  • Certificates tab is throwing Error calling OpenSSL tools error message
  • Incorporated new vRealize Cloud DLF
• Patch 11
  • View vRA > Infrastructure > Events > Event Logs - details result in 404 splash message on top middle of screen
  • After upgrade to vRA 7.6, unable to search deployment UI information related to multiple NICS or VM descriptions
  • Large sw_res_req tables cause slowdowns in query response times in larger environments
• Patch 12
  • vCACCAFEEntitiesFinder methods failing when running in parallel - exception: ‘java.lang.reflect.InvocationTargetException’
  • Re-submission of a failed request erases values inside the data grid of custom form
  • The subtenantID is not passed to vRO in payload when IAAS Form is submitted
  • Issue assigning an approval policy to a blueprint with a custom form and properties
• Patch 13
  • Custom Forms appearance tab for ’ visibility ’ conditional values do not show or hide a field on the request form
  • The on-demand networks have not been collected yet. Try reconfigure after they have been data collected
• Patch 14
  • Email notifications fail to work properly over time requiring service restarts

For the full details on this patch or to download the patch, view the VMware KB: Cumulative Update for vRealize Automation 7.6 (70911).

To download the latest cumulative security update for vRealize Automation and vRealize Orchestrator 7.6, visit the VMware Product Patches site and search for vRealize Automation 7.6.0.

Share:

Search

Get Notified of Future Posts

Follow Me

Recent Posts