Updated 10 November 2020

vRealize Automation 8.0 | 29 OCT 2019 

  • vRA Easy Installer (ISO) build 14878991
  • vRA product (appliance)  build 14842736

Check for additions and updates to these release notes.

What's in the Release Notes

About vRealize Automation 8.0

vRealize Automation 8.0 brings the vRealize Automation Cloud capabilities to the on-premises form factor, opening up the possibility of consuming vRealize Automation in SaaS or on-premises. This release modernizes the vRA 8 architecture and capability set to enable enhanced agility, efficiency, and governance in the enterprise.

What's New

This is the next major release of vRealize Automation.

This release of vRealize Automation uses a Kubernetes based micro-services architecture. The new release takes a modern approach to delivering hybrid cloud management, extending cloud management to public clouds, delivering applications with DevOps and managing Kubernetes based workloads.

The many benefits of vRealize Automation 8.0 include: 

  • Modern Platform using Kubernetes based micro-services architecture that provides
    • Simple install footprint for both non-HA and HA configurations
    • Scalable to meet modern workload challenges
  • Easy to setup and consume multi-cloud infrastructure surface
  • API-first approach to deliver cloud automation
  • Deliver Infrastructure-as-Code using a declarative YAML syntax
  • Iterative development of blueprints 
  • Cloud Agnostic Blueprints
  • Collaboration across teams via sharing of objects
  • Self-service catalog coupled with agile governance
  • Simple policies
  • Native support for SPBM policies 
  • Deploy IPv6 workloads on dual-stack IP (IPv4/ IPv6) networks in vSphere 
  • CI/CD pipeline and automated application release management
  • Kubernetes/container management
  • New Action based extensibility (ABX), which allows you to write lightweight scripts, using Node.js and Python.
  • Git Integration to manage all blueprints, workflows, actions and pipelines.
  • Workload on-boarding with existing data center VMs
  • New Migration from vRealize Automation 7.5 or 7.6 assessment
    • The ability to upgrade or migrate from vRealize Automation 7.5 or 7.6 to vRealize Automation 8.0 is not available in vRealize Automation 8.0.
    • You can only perform a migration assessment on your source environment and any embedded vRealize Orchestrator instances to determine the migration readiness of your vRealize Automation 7.5 or 7.6 source environment. The migration assessment alerts you to any system object and its dependencies that are not ready for migration. See System Objects.

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.0 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.0 product documentation.

In-Product User Assistance

VMware vRealize Automation 8.0 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.

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.0 product documentation.

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

Known Issues

The following known issues are present in this release.
  • vRA 8.0 cluster fails to start after VAs have been reverted to a snapshot

    Snapshot of 3-node vRealize Automation 8 cluster from within LCM is currently unavailable.

    Workaround: Shutdown vRA services before taking an offline snapshot

    1. Run "/opt/scripts/deploy.sh --onlyClean" on a single vRA node to shutdown the services safely.

    2. Power off each node using the halt command.

    3. Take a snapshot after the vms are powered off.

    Startup procedure when environment is reverted to snapshots:

    1. Power up all vms.

    2. Run the "deploy.sh" script with no arguments for vRA services to come back up.

  • 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).

  • Document limitation/workaround for cost estimation using multiple disks(if using count property in blueprint)

    Currently, in vRA8.0, Day 0 provisioning of disks with count property is broken as the blueprint UI doesn't generate new syntax for the attached disk in yaml format. As a result, one of the mandatory property of disk cost estimation, i.e. vcUuid, is null and prevents costing estimation for the catalog item.

    Workaround: Manually update the syntax of the blueprint in yaml if using count property for disks:

    attachedDisks: ‘${map_by(resource.Cloud_Volume_1.id, id =>


  • Deploying a blueprint with volume attached to a compute instance and an added count property to have multiple disksm results in some disks being DETACHED. 

    When deploying such BP, post provisioning, for the created deployment(e.g. count: 2), one of the disks always remains DETACHED instead of ATTACHED. Ideally, only the latest syntax(map_to_object(resource.disk[*].id)), in case of multiple disks as the value for "attachedDisks" property, should be allowed.Cost estimation is also not supported in the catalog UI and results in error if such blueprint gets published as a catalog.

    Workaround:Add the count property with required number of disks and then only create a link between disk and machine in the blueprint canvas. This method ensures yaml always gets the latest syntax for attachedDisks property.Otherwise, you must manually update to a newer syntax when using count property for adding multiple volumes, once the disk is attached with a compute instance.The correct syntax to be updated in blueprint manually is: attachedDisks: '${map_by(resource.Cloud_Volume_XYZ.id, id => {"source":id})}'

  • ABX might not work if Internet access sits behind a Proxy

    In vRA 8.0, ABX actions are executed in prepared on the fly containers that run inside the vRA appliances.

    The preparation of these containers require automatic downloads of artifacts that are available in public repositories as industry standard delivery mechanism.

    vRA deployments that would like to take benefit of ABX actions should be assigned to virtual networks that have open access to such repositories. Identical network configurations are required for all 3 nodes, when vRA is deployed in cluster. 

    An example of standard repositories that should be accessible via direct internet access or through a proxy:

    For all actions: https://symphony-docker-external.jfrog.io & https://gcr.io & https://hub.docker.com/

    For Python actions: https://pypi.org/

    For NodeJS actions: https://registry.npmjs.org/

    Opening access to additional repositories might be also required based on the actual dependencies of the ABX actions.

    These requirements also apply to the default IPAM and AD provisioning configuration in vRA, which is backed by ABX actions.

    Workaround: Use a HTTP proxy to pass traffic to the required external sites. It is configured through vracII proxy command line extension and the additional instructions can be obtained via GSS.

  • Cannot set wildcard certs for certain domain names, specifically those not using a Public Suffix.

    vRealize Automation 8.0 supports setting a wildcard certificate only for DNS names that match the content of the Public Suffix List ([https://publicsuffix.org/]) For example, a valid wildcard certificate: you can use a wildcard certificate with DNS name like "*.myorg.com". This is supported because "com" is part of the Public Suffix List. An invalid wildcard certificate example: you cannot use a wildcard certificate with DNS name like "*.myorg.local".This is not supported because "local" is not part of Public Suffix List. 

    Workaround: Only use domain names in the Public Suffix List.

  • Directed to Cloud.vmware.com for access

    The No access error page is shown for logged in user with rights in organization.This only occurs in HA. 

    Workaround: Clear browser cache. 

  • vRO workflow with input from type 'properties' can not be triggered 

    If a vRealize Orchestrator workflow, with input from type properties is exposed in catalogSteps, and is then triggered from vRealize Automation catalogResult, the run fails.

  • vRealize Automation has limitations when running certain vRealize Orchestrator workflows from the catalog. 

    Currently supported workflow input and output types are: String, Boolean, Date, Number, SecureString, Array/String, Reference Type

    Workaround: Use vRealize Orchestrator workflows that include inputs/output parameters of the supported types.

  • Provisioning fails with EBS topic not registered after stopping the primary db node

    In a vRealize Automation 8 HA environment, after removing the primary db node, provisioning fails with following error: "Failed to publish event as EBS topics are not registered".

    Workaround: See KB for more information.

  • NEW Link to Migration Guide on the Migration Assessment Getting Started page is invalid

    The link to the migration guide in the Migration Assessment UI is incorrect and invalid,

    Workaround: The correct link is Using the vRealize Automation 8 Migration Assessment Service.

  • NEW 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.

  • NEW 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.

  • NEW 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".

check-circle-line exclamation-circle-line close-line
Scroll to top icon