vRealize Automation 8.2 | Updated 05 May 2021

  • vRA Easy Installer (ISO) build 16982088
  • vRA product (appliance)  build 16980951
  • vRA update repository build 17018654

Check for additions and updates to these release notes.

What's in the Release Notes

New vRealize Automation 8.2 Patch 1

vRealize Automation 8.2 Patch 1 is now available and includes bug fixes in different areas. This is a cumulative update. 

For more information and installation instructions, see KB 81396.


Upgrade failure after performing steps in KB 87120

Performing the instructions used to address the CVE-2021-44228 and CVE-2021-45046 log4j vulnerabilities described in KB 87120 can cause upgrade failures for vRealize Automation and vRealize Orchestrator 8.6.2 or earlier. For a workaround, see KB 87794.

About vRealize Automation 8.2

vRealize Automation 8.2 adds to the vRealize Automation 8.1 capabilities to bring it closer in capability to the vRA 7.x release, reintroducing key capabilities like XaaS and adding capabilities such as AWS GovCloud support and Powershell support in ABX and python, node.js and Powershell in vRO.

Required: Before upgrading to vRealize Automation 8.2, you must apply Product Support Pack 1 on vRealize Suite Lifecycle Manager 8.2. vRealize Suite Lifecycle Manager Product Support Pack 1 is an accumulative support pack for vRealize Network Insight 6.0.0. This support pack also provides support for vRealize Automation 8.2 upgrade bundle and vRealize Automation Upgrade OVA files, which is required for scaling out vRealize Automation 8.2 post upgrade from vRealize Automation 8.1 or earlier versions to vRealize Automation 8.2. Refer to KB article 79105 to map vRealize Automation 8.2 upgrade OVA bundle binary under the patched product binaries in the user interface of vRealize Suite Lifecycle Manager.

Before upgrading, review the required System Resources and ensure your system meets these requirements.

Deployment service has released new versions of the Catalog, Deployment, and Policies APIs. Be sure to check API version compatibility.

Note: vRealize Automation 8.1 did not require you to accept a source certificate during migration assessment. As a result, you must reassess your source environment. To reassess your source environment and accept the source certificate: delete the source environment, re-add it, accept the certificate, and reassess the source environment using the migration assistant service.

What's New

vRealize Automation 8.2 includes many new benefits.

New Version of the vRealize Automation REST API

A new version of the vRealize Automation REST APIs is available with all vRealize Automation releases. The new version increases resource support to 300 resources per deployment and provides performance improvements. If you are an API user and have not locked your API to a version before, you might encounter an unexpected change in an API response. As a best practice, assign the apiVersion variable to lock your API to the version you want to use. For example:

  • To lock your APIs to the vRealize Automation 8.1 APIs, use apiVersion=2020-04-16
  • To lock your APIs to the vRealize Automation 8.2 APIs, use apiVersion=2020-10-06

If left unlocked, your API requests will default to the latest version which is apiVersion=2020-10-06.

For information on how to lock you APIs to a specific version, see the "API Versioning" section of the vRealize Automation 8.2 API Programming Guide.

Note: The vRealize Orchestrator REST API do not support the apiVersion parameter and are backward compatible.

vRealize Automation Blueprint name change to VMware Cloud Templates

  • Blueprints are renamed to VMware Cloud Templates. Learn more.

  • You might still see the term Blueprint in the official documentation, API, error messages, and other areas of code.

VMware vRealize Automation 8.2 includes in-product user assistance

  • Use the signpost help to learn about a setting.
  • Use the help panel to get more information about a feature or configuration process.

Migration Assistant Availability

Extended migration assessment service capability to allow the user to migrate content and deployments from a vRA 7.4/7.5/7.6 instance to a vRA 8.2 instance.

  • Migrate infrastructure, subscriptions and deployments
  • Rollback a migration
  • Incrementally migrate individual Business Groups in stages without migrating the entire vRA 7.x system at once

Restriction: The vRealize Automation 8 migration assistant does not support migration with an external vRealize Orchestrator instance.

Terraform Configuration as a VMware Cloud Templates Resource in vRealize Automation 

Terraform open source configurations are now integrally supported by VMware Cloud Templates. Cloud Administrators can integrate Terraform configurations stored in Git and release as self-service catalog items. Select capabilities include the following:  Learn more

  • Create Cloud Templates with Terraform configurations
  • Compose hybrid Terraform-VMware Cloud Templates
  • Enable built-in power Day 2 actions and custom day 2 actions on Terraform resources
  • Central deployment state file
  • Managed Terraform runtime in cloud
  • Code Stream pipeline to deploy Terraform based Cloud Templates for DevOps users

SDDC Manager Integration and VMware Cloud Foundation (VCF) cloud account

Configure SDDC Manager integration and on-board workload domains as VMware Cloud Foundation(VCF) cloud accounts into VMware Cloud Assembly service. A VCF cloud account enables you to incorporate a VCF workload into Cloud Assembly to facilitate a comprehensive hybrid cloud management solution.

  1. SDDC Manager can be as an integration endpoint once for onboarding one or more workload domains as VCF cloud accounts.
  2. VCF cloud accounts bring in both Compute and Network resources (vSphere and NSX-T) into vRealize automation for provisioning new resources.
  3. VCF cloud accounts support service credentials to automatically create a new service account to use with vSphere and reuses the existing NSX credential from SDDC Manager.
  4. Flavor, Image, Network and Storage profiles can be defined for VCF cloud accounts similar to vSphere and VMC cloud accounts.
  5. Use vSphere/NSX specific or agnostic resources with constraints to direct the provisioning of new resources into VCF cloud accounts.

Multi-tenancy: Centralized Management of Tenant Infrastructure 

Setup and manage Virtual Private Zones and share IaaS resources across projects while maintaining tenant isolation. For managed service providers, shared infrastructure multi-tenancy ensures optimal resource allocation and control. This capability enables a provider to allocate provider-managed infrastructure to their tenants. Currently this is only supported for provider organizations in Multi-Tenancy configuration through VMware Cloud Provider Hub. Learn more.

  1. Provider administrator creates a bundle of isolated IaaS resources (Compute, Network, Storage, Image, and Flavor) called the Virtual Private Zone (VPZ). All CRUD operations are supported.
  2. Provider administrator shares the VPZ with a tenant.
  3. Tenant administrator, in turn, shares the VPZ with a project within the tenant org. Note that multiple VPZ can be added to a single project.
  4. Tenant project members can provision a machine into the VPZ.
  5. Project members view the deployment and see an "obfuscated" view of the underlying infrastructure (only the VPZ name).
  6. Tenant A resources are not visible to Tenant B, even when underlying infrastructure is shared.

Custom Role Based Access Control (RBAC) 

vRealize Automation 8.2 introduces Custom roles based access that enables customers to closely align the roles they assign consumers and providers to the actual roles they hold within their organizations. It helps with configuring restrictive enough roles, based on the actual tasks (permissions) users are eligible for and resource they are eligible to without overloading permissions with unnecessary tasks or confront organization security.

Base concepts:

  • Org admins are able to define custom roles within organization.
  • Each custom role can be assigned to an organization users/group.
  • New custom roles model integrates with out of the box roles and works in collaboration with access control and policy within the organizations.

Available configurable permissions:

  • Custom Roles for Images, Flavors, Zones, Machines and Requests, Cloud Accounts, Cloud Zones and Projects
  • Custom Roles for Manage and View Onboarding Plans
  • Custom Roles for Extensibility use cases:
    • Manage and View
      • Action Runs
      • Actions
      • Subscriptions
    • Viewer permissions for:
      • Events
      • Event Topics
      • Workflows
      • Workflow Runs
  • Custom Roles to Manage and View Cloud Templates
  • Custom Roles to Manage and View Custom Day2 for built-in & custom resources
  • Custom Roles for Pipeline Modeling, Execution, and Configuration
  • Custom Roles for Policy Permissions
  • Custom Roles to manage permissions for approvals

Refer to custom roles and examples of how they work with the other roles for more information.

XaaS Custom Resource and Custom Action Enhancements

  • Custom Resources Schema Dynamic data support. vRealize Automation 8.2 now includes automatic validation for the workflows added as lifecycle actions to your custom action. This feature also includes improvements to the external type property and custom resource property schema. Learn more.
  • Custom Day 2 actions bindings. vRealize Automation 8.2 supports three types of action bindings: in request, with binding action, and direct binding. Learn more.

Support 1:N Association Between NSX-T Manager and vCenter

Support for 1 NSX-T manager connected to multiple vCenters. Learn more.

NSX-T Policy Mode Support 

  • Enable the creation of a new NSX-T endpoint in Policy mode. Learn more.
  • Policy mode support for Networks (Day 0, Day 2), Load Balancers (Day 0), Security Groups (Day 0), Tagging (Day 0), VM Scale In/Out (Day 2), and Port Forwarding (Day 0, Day 2).

NSX Load Balancer Configurations - Logging Level, Algorithm, Type, NIC, and VIP 

  • Support for NSX Load Balancer advanced configurations, including Logging level, Algorithm, and Type (Day 0, Day 2). Learn more.
  • Support for NSX Load Balancer configuration options for NIC for all network types, including private, existing, public, outbound and routed networks. Load Balancer can now be connected to a specific machine NIC, rather than always using the first NIC in the machine by default. 
  • Ability to specify the IPv4 VIP (Virtual IP) in the Cloud Templates; this would allow Load Balancer to have a specific IP, instead of an IP from a static IP range.

NSX Port Forwarding

  • Port Forwarding (DNAT rules) support for NSX outbound networks. vRealize Automation now exposes a new Cloud.NSX.Gateway Cloud Templates resource type that allows the DNAT rules to be specified for the gateway/router connected to the outbound network. Learn more.
  • Day 2 actions support for adding new NAT port forwarding rules, reordering rules, editing existing rules, and deleting rules.

Networking Day 2 – Reconfigure Security Groups

  • Reconfigure security groups:
    • Change security groups - add a new or existing security group, remove associated security groups, and modify
      associated security groups. Security groups are part of deployments for day2 actions. The day2 actions are supported for a single machine only and not for a multi-machine cluster.
    • Delete security group - remove security group from deployment. If the security group is on-demand, then it is destroyed.
  • Move VM between networks:
    • Update deployment constraints on the vSphere machine NIC to move it from one existing network to another existing network in the same network profile.
    • Machine can be moved from static to static network, or dynamic to dynamic network.
    • The previous network is deleted from the deployment. Learn more.

vSphere 7 Supervisor Namespace as a Catalog item

  • Ability for catalog user to request vSphere supervisor namespaces from the vRealize Automation catalog powered by an underlying VMware Cloud Template.
  • Cloud Templates author can define supervisor namespace resource limits on the Cloud Templates resource. This allows the admin to restrict user resource consumption.

ITSM Plug-in 8.1.2

  • New ITSM plugin (version 8.1.2) for vRealize Automation is now available on ServiceNow store.
  • Orlando Support – Plugin supports Orlando which is latest ServiceNow version. It also supports previous ServiceNow versions Madrid and New York.
  • Support for Custom Forms in User Portal
  • Multi-level Approval – The ServiceNow administrator can configure multi-level approval for ServiceNow Catalog requests. 
  • Email Notifications – The ServiceNow administrator can configure email notifications for various activities like Deployment Requests, Approval Requests, Day 2 Requests, and Endpoint and Entitlement configurations.
  • Auto Create tickets for failed deployments – A support ticket is created and assigned to support groups in ServiceNow whenever a deployment request fails in vRealize Automation or a day-2 action fails.

vRealize Automation Scaling

  • Up to 250 resources per deployment and 400,000 virtual machines.
  • If you anticipate deployments to have more than 100 resources, upgrade to the new API version 2020-08-25.

First Class Disk and IaaS APIs

  • Create a First Class Disk (FCD) disk object independently without a VM. Full support for CRUDL functionality - Create, Edit, Delete, List
  • Support for Day 2 actions and disk snapshot life cycle management
  • IaaS API to create, delete, list, attach and detach FCD.
  • IaaS API to convert existing disk to an FCD. Learn more.
  • IaaS API for FCD snapshot management (Create, Delete, List, and Restore). 

Extensibility Subscriptions

Support for up to 50 blocking and 50 non-blocking subscriptions per event topic. Learn more

Approvals For Catalog Items in Service Broker, Onboarded Deployments And Cloud Assembly Deployments

  • Approvals now apply to all catalog items beyond Cloud Assembly Cloud Templates, including Cloud Formation Templates, vRO workflows, ABX actions, OVAs, etc.).
  • Trigger approval policies based on the attributes of underlying resources filtered by: cloud account, cloud type, flavor, image, region or resource type. Learn more
  • Support approval flow for pre-provision and day 2 actions for cloud assembly blueprint deployments
  • Support approval flow for day 2 actions on imported deployments
  • More information about approval policies

Show Request Form in Approval Details

Approver can now see the input parameters the requester submitted as part of the approval request. This enhanced view helps the approver make the approval decision based on the same information the originator of the request provided.

Integration With vROps

When customers subscribe to both vRA Cloud and vROps Cloud, the integration gets automatically configured to provide the following benefits:

  • Support for advanced workload placement based on vROps policies.
  • Pricing for resources, deployments and projects for VMware Cloud.
  • Infrastructure health & performance metrics for VMware Cloud. Learn more

IaaS API Filter Resources Within Particular Region In Cloud Accounts

Resources in Cloud Assembly IaaS API can be found by the region that they belong to using Data filter. The region can be uniquely identified by the externalRegionId and the corresponding cloudAccountId.

API for Updating Cloud Account Password

Update cloud account password for vSphere and NSX using IaaS API.

Bitbucket integration support

Support for integration with on premises Bitbucket to use as a Git-based repository for ABX action scripts and VMware cloud templates.

Active Directory integration improvements

  • During the validate phase of the Active Directory, the Base DN search has been limited to containers only.
  • Certain customers were impacted due to ad-blockers which caused some Active Directory API’s to not load on Projects/Integration page. Those APIs have been adjusted so that now it works seamlessly with ad-blockers.
  • Project renames are now reflected under project association for an Active Directory Integration.

Custom property update via API

Update custom property for machines through IaaS API

vRA Log Retention Improvements

​On-premise logging infrastructure improved to include:

  • Seven days of log retention for each service
  • Service logs in a separate partition to conserve storage space
  • Logging infra extracted out of K8s layer to be able to collect logs if K8s is down

Custom Day 2 Actions

Custom day 2 operations for custom resources and vRealize Automation built-in types. Learn more

Custom Resources

Support for custom resources based on vRO types. Learn more

Deployment History

View and filter deleted deployment history for up to 90 days after deletion. Learn more

Share ABX Across Projects

Ability to share a single action-based extensibility across multiple projects. Learn more

Double encoding of the space symbols in oData queries is not necessary

The URL encoding behavior for IaaS API oData queries now work consistently with the modern internet search engines like Google. Before this change, double encoding was required for special symbols (%2520 and +).  Now there is no need to double-encode space symbols.


If you previously had the following query: {{url-home}}/iaas/api/machines?$filter=externalRegionId%2520eq%2520%27Datacenter%3Adatacenter-21%27 

Now this query should be changed to:  {{url-home}}/iaas/api/machines?$filter=externalRegionId%20eq%20%27Datacenter%3Adatacenter-21%27


If you want to search for 'symbol' – you should escape it by an additional quote

Search for '&' symbol – not supported in oData queries for CloudAccounts

Search for '%' symbol – not supported for all endpoints.

Custom Forms in Service Broker

If a workflow is imported in Service Broker and has a custom form enabled before enabling Properties and Composite types and the array counterparts were implemented, the custom form needs to be deleted and the workflows imported again in Service Broker to fix the elements in the form.

Configuration Management with VMware vRealize Automation SaltStack Config

VMware vRealize Automation SaltStack Config (formerly SaltStack Enterprise) is a configuration management system that maintains virtual machines in defined states. With the addition of SaltStack Config in vRealize Automation 8.2 release, you can now ensure that specific packages are installed and that any drift from the defined state is quickly addressed. You can also use SaltStack Config to query and execute commands either on individual VMs or groups of VMs at high scale and speed. For information about installing and using the product, see the SaltStack Config section of vRealize Automation 8.2 product documentation.

Before You Begin

Familiarize yourself with the supporting documents.

After installing vRealize Automation and setting up your users, you can use the Getting Started and Using and Managing guides for each of the included services. The Getting Started guides include an end-to-end proof of concept. The Using and Managing guides provide more in-depth information that supports your exploration of the available features. Additional information is also available in vRealize Automation 8.2 product documentation.

NEW The following tutorials are included in the Cloud Assembly documentation:

For information on vRealize Orchestrator 8.2 features and limitations, refer to the vRealize Orchestrator 8.2 Release Notes.

At VMware, we value inclusion. To foster this principle within our customer, partner, and internal community, we removed non-inclusive language in our documentation.

Customers that upgraded to vRealize Automation 8.2 using the new upgrade bundle might see errors during scale out (similar to patched environments). As mentioned in KB 79105, the ova bundle is hosted on my.vmware.com.

NEW If using VMware Identity Manager 3.3.3 with vRealize Automation 8.2 P1, you cannot use an IWA (Integrated Windows Authentication) with an embedded Linux connector. vRA 8.x Customers using LDAP or IWA with the external Windows connector are not impacted. For more details refer to KB 82013.

Resolved Issues

  • Blueprints with property bindings to certain networking properties fail to deploy because the binding values cannot be resolved correctly.

    Property bindings for the dns, dnsSearchDomains, and gateway properties are not working. These are primarily used with OVF blueprints.

    Workaround: Blueprints using the following properties must be modified to use a different set of properties.

    Note: A permanent fix for this issue will be delivered in the first hotfix for vRA 8.1. The workaround provided here should be considered temporary and will need to be reverted after the hotfix is applied.

    For the dns property:

    dns0: '$\{resource.Cloud_NSX_Network_1.dns[0]}'
    dns1: '$\{resource.Cloud_NSX_Network_1.dns[1]}'

    must be changed to

    dns0: '$\{replace(split(resource.Cloud_NSX_Network_1.dnsServerAddresses, ",")[0], "[", "")}'
    dns1: '$\{replace(split(resource.Cloud_NSX_Network_1.dnsServerAddresses, ",")[1], "]", "")}'

    For the dnsSearchDomain property:

    dnsSearchDomain0: '$\{resource.Cloud_NSX_Network_1.dnsSearchDomains[0]}'
    dnsSearchDomain1: '$\{resource.Cloud_NSX_Network_1.dnsSearchDomains[1]}'

    must be changed to

    dnsSearchDomain0: '$\{replace(split(resource.Cloud_NSX_Network_1.dnsSearchDomains, ",")[0], "[", "")}'
    dnsSearchDomain1: '$\{replace(split(resource.Cloud_NSX_Network_1.dnsSearchDomains, ",")[1], "]", "")}'

    For the gateway property:

    gateway: '${resource.Cloud_NSX_Network_1.gateway}'

    must be changed to

    gateway: '${resource.Cloud_NSX_Network_1.gatewayAddress}'


  • Node's CPU usage jumps to 100%, pods start crashing

    When trying to generate a log bundle on a highly-loaded environment, it is possible to temporarily overload one or more of its nodes in terms of CPU and/or memory usage. This may cause services to crash.

    Workaround: Run the log bundle collection script when the environment is not loaded. Configure and monitor log forwarding to an external logging solution (vRLI or syslog server).

  • Data collection fails to collect storage policies, and fails to update existing storage policies with compatible datastores or vCenter 7.0. Data collection fails to update WCP availability in vRA.

    If there are multiple datacenters in a vSphere cloud account and not selected in vRA's endpoint, this could cause failures towards completing the data collection and the data collection is partially successful and causes above symptoms.

    Workaround: Select all datacenters (regions) in vSphere cloud account. If there is no intention to manage that datacenter, you don't need to create the cloud zone. However the datacenter's artifacts will be collected.

  • Binding of Custom day2 action for vSphere built-in type needs to be manually referenced

    In vRA 7.X there was an automating binding of Custom day2 action and in context vRA built-in object. In vRA 8.1 this binding should be made via vRO action.

    You can check the official documenation for more guidance on the binding process.

  • When a deployment is missing a resource and the user tries to update the deployment by applying a blueprint in generation of plan, the user might see the "Another request is already in progress on deployment" error message.

    The user will also see an additional "Day 2 Action - Delete" in the deployment history timeline. Also, when user tries to update the deployment via API they see "Another request in progress on deployment". 

    Retry updating the deployment.

  • When importing a vRO workflow as XaaS catalog item that has actions which populate dropdowns, selectable values are imported as static constants

    When importing a vRO workflow as XaaS catalog item that has actions which populate dropdowns, selectable values are imported as static constants.

    This means that when the user requests the catalog item, the request form is presented with static values rather than dynamically populated fields.

    For such catalog items use custom forms and manually select "external source"  and browsing action which will populated the value correctly.

  • vRA 8.1 Deployment or upgrade fails when the appliance is deployed in a 172.17.x.x network

    vRA deployment fails - deploy.sh script failure at the "Registering embedded vRO" stage
    /var/log/deploy.log contains:
    curl: (22) The requested URL returned error: 400 Bad Request
    Failed to register vRO. Will retry in 45 seconds...
    curl: (22) The requested URL returned error: 400 Bad Request
    Maximum number of retries exceeded."

    Cause: The appliance got an IP address from the 172.17.x.x space. This conflicts with in internal docker0 interface from the vRO pod

    Refer to https://kb.vmware.com/s/article/78783

  • When filtering a list of load balancers by name, the same vRA-deployed NSX load balancer appears twice with slightly different names - once as "Deployed" and again as "Discovered".

    When vRA deploys an NSX load balancer, the load balancer is created in NSX using a different ID and name than vRA uses in its internal database. As a result, vRA creates and subsequently updates a new, duplicate load balancer record when it data collects the associated NSX cloud account instead of updating the load balancer record it originally created. This results in the confusing appearance of near-duplicate pairs of load balancers in screens where load balancers are listed.

    Workaround: When adding a vRA-deployed NSX load balancer to a network profile, select the one that is "Deployed" instead of the one that is "Discovered".

  • Unable to update the "useSudo" option for Ansible integration

    User cannot edit the "useSudo" option for Ansible integration accounts in the UI


  • Randomly getting unknown error even if the Ansible playbook execution is completed successfully

    When checking the status of the Ansible playbook, the ssh connection to the proxy may fail due to overloading, a retry mechanism is introduced in case of connection failure to avoid the random error.


  • Ansible inventory updates failing with "IP not found in inventory "

    Concurrent executions may result in inventory file not being updated correctly, which causes the failure since hosts are not found in inventory.


Known Issues

The following known issues are present in this release.
  • vRA deployment fails to initialize on new setups from Easy Installer

    vRA deployment (single or clustered) fails to initialize on new setups from Easy Installer or vRealize Suite LCM
    The error shown in LCM is LCMVRAVAVACONFIG590003

    Workaround: Retry cluster initialization from within vRealize Suite LCM.

  • When a vCenter cloud account is updated to add a data center, the resources from this data center are not immediately available for use.

    Changes made to regions (data centers) for a vCenter cloud account do not take immediate effect and require data collection to run.

    Workaround: Wait for the next data collection to complete successfully. Data collection runs approximately every 10 minutes.

  • PowerShell tasks appear to be stuck

    When there is no active session PowerShell tasks appear to be stuck. This behaviour is seen because the PowerShell process responsible to run the user script is held by windows system process WmiPrvSE.

    Workaround : Login to the system and keep an active session. Lock the screen instead of completely logging out.

  • vRO represents Array types as complex types with only one column, rather than a field whose "type.isMultiple" is true.

    When adding a workflow which has an array input and consequently customizing its form, do not change the ID of the column in the Values tab of the data grid. The default value must stay set at _column-0_ . Conversely, you can change the label of the column (which is visible in the UI when adding values to the datagrid).

  • License re-configuring is not supported.

    After configuring vRealize Automation with the Enterprise license, the system can not be re-configured to use the Advanced License.

  • vRealize Automation 8 does not support Internet Explorer 11

    You cannot use Internet Explorer 11 with vRealize Automation 8.

    Workaround: Use a different browser instead of Internet Explorer 11.

  • BP Canvas is not refreshed after custom resource has been changed or deleted.

    If you delete a custom resource, the change is not propagated to the Blueprint canvas immediately.

    The Canvas has a cache mechanism, which can be updated after using refresh button, next tot he search pane.

  • Create different custom resources with the same vRO object type is not supported

    In vRA 7.X it was possible to create different custom resources for the same type. This allowed users to define a different set of create / delete / operate actions for the same vRO type with creating different custom resource types. In vRA 8.1 We do not support a case where same vRO_Type can be leveraged from different custom resources. 

  • vRO workflow is not executed through catalog when there is empty input with reference type

    Null pointer exception appears on attempt to request  vRO Workflow with and empty value for the Workflow input with a reference type.

    Workaround: Set a default value for the reference type or make the field mandatory.

  • Unsuccessfully provisionined custom resource can't be deleted from a deployment

    When you request a custom resource, if the workflow run that creates the resource fails, a resource in the deployment service is still created (since we are replying to the initial request with a STARTED status which in turn creates the resource in deployment). This resource cannot be deleted since it doesn't contain the metadata that is added upon successful provisioning of the resource in vRO.

    Workaround: Right after the first attempt to delete the custom resource, a dialog appears which asks you whether you want to force deletion. Say yes to force its deletion.

  • Custom Resource Name is not propagated correctly to the deployment view list

    When you create a custom resource based on vRO_Type, you usually use a comprehensive display name. Currently this display name is not available in the Deployment view. The resource, which appears in the deployment is identified only by its type.

  • Available option to set timezone from vCenter Machine Console window

     Undefined behaviour when user sets timezone from vCenter Machine Console window

    Workaround: Don't change the time zone.

  • Tenant Names with different cases are treated the same way

    A tenant named vmware and another one named VMware are seen as the same.

    Workaround: Tenants in vRA 8.1 are based on hostnames since hostnames are case insensitive the tenant names are also case insensitive. This means that a tenant named VMware is the same as VMWARE or vmware or any other combination cases. The tenant name capitalization may vary and may not be preserved across the application.

  •  vRO Workflow presentation with an OGNL expression does not render properly when used as a custom day2 operation in vRA.

    Custom Resource Actions with workflows that have OGNL constraints in their presentation may not render properly and it may not be possible to populate all required fields.

  • Cost\Price functionality does not work with shared infrastructure multi-tenancy

    The pricing functionality might report inaccurate results when configured to a multi-tenant deployment where tenants can share infrastructure resources. This is because pricing does not recognize multi-tenancy.The price is calculated only for the org for which vROPs is added and deployments are created. 

  • Migration Assessment of a single vRealize Automation 7.x installation into multiple vRealize Automation 8.2 organizations requires manual certificate acceptance.

    This occurs when you attempt to migrate a single vRealize Automation 7.x environment into multiple 8.2 organizations and your source vRealize Automation 7.x installation has configured an insecure SSL certificate.

    Workaround: For information and workaround steps, see KB 81062.

  • Assessment Service swagger is not available

    The assessment service swagger page is not available.

    Workaround: Run the assessment through the migration API listed on the migration swagger page.

  • Deployments with an existing network fail during allocation on vSphere / NSX-v cloud accounts when DRS is disabled on the vSphere cluster.

    When selecting an NSX-V network in the network profile and requesting a deployment with an existing network, the deployment fails during allocation with the message: "Unable to find a common placement for compute...with the network configuration...". This occurs when the vCenter contains clusters with DRS disabled.

    Workaround: Enable DRS on the cluster and include the cluster in the vRA cloud zone, or select a vSphere network in the network profile.

  • Under certain circumstances, scaling in or out a load balanced machine cluster fails with a cryptic error message

    When scaling in or out a load balanced machine cluster where the load balancer contains "loggingLevel" or "type" properties with different values than the same properties on the parent (IaC) load balancer, the operation fails with the following message:

    Update operation is supported for one property at a time

    Workaround: Remove the "loggingLevel" and "type" properties from the load balancer in the blueprint and then perform the scale operation.

  • The policy details page shows empty value for "Role" when a custom role is deleted.

    After deleting a custom role, when a user navigates to viewing the details of an existing Day 2 policy, the page should display a message reflecting that the role was deleted. However, the value for "Role" is empty.


  • Image enumeration fails for migrated Amazon Gov Cloud account.

    After the AWS Gov Cloud endpoint is migrated from vRA 7 to vRA 8.2, user will note that the image enumeration of the cloud account fails.This issue occurs because all regions in the cloud account page are selected.

    Workaround: After migration, navigate to the new AWS Gov Cloud account. Edit the account and deselect the general regions. Keep only the Gov Cloud related regions and save the configuration. Further Image Enumeration will be done successfully.

  • Service broker forms do not populate default values set in vRO workflow input

    When vRO workflow has a string input set with default value ,it does not get automatically propagated in the request form when starting the workflow from service broker.

    Workaround: Set the given default value using service broker Custom forms.

  • Service Broker cannot import vRO workflows that have actions in valueList for a string field

    Schema for string field that contains valueListpopulated by an action cannot be parsed and imported in Service Broker


  • Pulling Docker Images Behind Proxy requires additional configuration

     In vRA 8.2, ABX service pulls container images from publicly available Internet repositories. If vRA is deployed on an isolated network that does not allow outbound traffic to public sites, a HTTP proxy must be configured. While vRA 8 enables proxy configuration via its CLI, the workflow does not include an automatic setup for the docker service.

     Workaround: Such configuration should be made separately. KB article to be determined.

  • Complex objects with type anyOf are not supported in cloud template request forms

    If the form contains anyOf property for a complex object, anyOf will be visualized as a string dropdown instead of different sets of constrains to validate the input.

    Workaround: Use Enum type instead of anyOf values.

  • Exception in input dialog if properties not defined in object type schema

    If input property is of object type and properties is not defined in json schema, the input dialog in test or deploy blueprint dialog would not load.

    Workaround: Either remove default value from input property, or define properties schema in the input property with default value. The fix should be available in 8.2 P1.

  • Cannot send value while deploying with input array field

    Although users can fill the values in input form, UI is sending array of null to blueprint service in test/deployment dialog.

    Workaround: Use object or string/number fields instead, the fix should be available in 8.2 P1.

  • After upgrading to vRealize Orchestrator or vRealize Automation 8.2, some resource elements in the vRealize Orchestrator Client might appear changed or reverted to an older version.

    After upgrading to vRealize Orchestrator or vRealize Automation 8.2, some resource elements in the vRealize Orchestrator Client might appear changed or reverted to an older version. This problem occurs with resource elements that were previously updated in the vRealize Orchestrator Client by using a different source file. After upgrading your vRealize Orchestrator or vRealize Automation deployment, these resource elements can be replaced by an older version. This is an intermittent issue.


    1. Log in to the vRealize Orchestrator Client.

    2. Navigate to Assets>Resources.

    3. Select the resource element affected by the problem.

    4. Select the Version History tab, and restore the element to the appropriate version.

    5. Repeat for all affected resource elements.

  • NEW vRealize Automation Version 8.2.0 Patch 1 Download Fails

    When downloading vRealize Automation 8.2.0 Patch 1 online, it may fail due to issues in the production Content Delivery Network (CDN), where vRealize Automation patch is hosted, and you may see the following error:

    LCMPATCHDOWNLOAD16001 Patch Processing failed

    Workaround: Perform the following steps to download vRealize Automation 8.2.0 Patch 1. Close the other patch downloads in progress when performing these steps.

    1. If there are any files in the /data/patches/temp/ folder of vRealize Suite Lifecycle Manager, delete the files.
    2. Trigger a patch refresh by navigating to Settings > Binary Mapping >Patch Binaries, and then selecting Check Patches Online in vRealize Suite Lifecycle Manager.
    3. Proceed with the patch download.
check-circle-line exclamation-circle-line close-line
Scroll to top icon