VMware vRealize Automation 8.0.1 – Hotfix 3 Released

Reading time: 2 minutes

It seems like it was just a few days ago that I was posting that vRealize Automation 8.0.1 Hotfix 2 was available. In reality, it was precisely 15 days ago. Nevertheless, on April 16, 2020, VMware released the third hotfix for vRealize Automation 8.0.1. Hotfix 3 (20 days after Hotfix 2) including seven fixes for Provisioning, the Service Broker, and vRealize CodeStream.

The hotfix can be installed using vRealize Suite Lifecycle Manager 8.0.1. It is recommended to install vRealize Suite Lifecycle Manager 8.0.1 Patch 1 before installing vRealize Automation 8.0.1 Hotfix 3 (Build For complete details on the items that have been resolved with this hotfix, review the VMware KB article Cumulative Update for vRealize Automation 8.0.1 (76805). 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.

Items fixed in this release include:

  • Provisioning
    • Insufficient storage error happens if multiple VMs are deployed with Storage DRS enabled.
    • Fix “deallocate resources” as part of the memory quota limit. 
    • Deployments not respecting the placement policy setting in some cases.
  • Service Broker
    • In the middle of a Terraform deployment, a token expiration can leave deployment stuck in progress, which can not be canceled.
  • vRealize CodeStream
    • Pipeline input properties have null values when triggered via Git Pull Webhook, reported for Github enterprise.
    • Timeout - getting error ‘connection timed out: /10.244.xx.yy:8000.
    • Pipelines will not run, hung on status ‘Not_Started’.

See Also


Get Notified of Future Posts

Follow Me

LinkedIn Icon
Twitter/X Icon
Threads Icon
RSS Icon

Recent Posts