On November 13, 2020, VMware released the first patch for vRealize Automation 8.2. Patch 1 including twenty-five fixes for the Provisioning Engine, the Service Broker, Migration and Assessment Services, vRealize Orchestrator, and virtual appliance/clustering.
The patch can be installed using vRealize Suite Lifecycle Manager 8.2. It is recommended to install vRealize Suite Lifecycle Manager 8.2 Patch 1 before installing vRealize Automation 8.2 Patch 1 (22.214.171.12470). For complete details on the items that have been resolved with this hotfix, review the VMware KB article Cumulative Update for vRealize Automation 8.2 (81396). To download the patch for import into environments not connected to the internet, visit the VMware Product Patches page, and select vRealize Suite Lifecycle Manager for the Product and vRA-8.2.0-PATCH for the Version.
Items fixed or enhanced in this release include:
Unable to onboard VMs that had a vSphere tag attached to them renamed
Handle empty strings for recoverRunnableId and recoverRunnableType, resulting in duplicate Action runs in a certain scenario
Fix handling of networkSelectionIds for multi NIC machines
vSphere enumeration doesn’t set subnetLink for machine NICs created outside of vRA
Failures observed in deployment when VM-Folder, where it’s supposed to be placed, has special characters
large scale - high CPU usage caused by provisioning requests
roles: Cloud Assembly User with “Manage Integrations” role not able to create (IPAM, AD) or tag an integration
roles: Cloud Assembly User + Project Member gets 403 forbidden viewing projects
Remote Console not working for deployments behind tenants in vRA 8.2
Resolved issue when adding 20+ projects for AD integration and Editing DNS
Disabled extensibility for “simulated” requests - was causing duplicate workflow runs when a deployment is requested
Reduce AutoConfigurer job only for AWS Autoscaled groups and spot instances.
Migration & Assessment Services
Get Notified of Future Posts