VMware vRealize Automation 8.0.1 - Hotfix 2 Released

Reading time: 3 minutes

On March 27, 2020, VMware released the second hotfix for vRealize Automation 8.0.1. Included in it are sixty-three fixes for items relating to the Provisioning, vRealize Orchestrator (vRO), vRealize CodeStream, and Virtual appliance/clustering.

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 2 (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
    • Request tracker for deployment shows a blank screen
    • Release IP address from the missing machine
    • Added IPv6 Check When Validating Security Group Rules
    • Fix project’s cloud zone memory limit not working with vSphere flavors
    • Deploying 190 machines in single deployment or 100+70 machines deployed in 2 parallel deployment - IPAddressAllocationTaskService very slow, high memory consumption leading to provisioning-service pod restarts
    • Disable AzureComputeProvisionWithBootAndAdditionalDiskWithNoConstraintsIT
    • Disable AzureWordpressProvisionNetworkIT, same as the master
    • Load Balancer From Kubernetes On Azure Causes Data Collection Failures
    • Disable symphony usage in pre/postflights
    • IP addresses remain outside the IP range, after down-sizing the range
    • Network [Automation_overlay_tz] doesn’t have an available block of IP addresses that is big enough to allocate a /24 subnet
    • Bump Azure network rest API version to support security rule multiport
    • Request tracker for deployment shows a blank screen
    • Cherry-pick fix to vra-medley-rel branch
    • Successful deployment with network shows spinning (in progress) on the infrastructure -> requests page is post-deployment event fails
    • Fix for bug Incorrect AWS requester tag for the deployed instances
    • Allow IP range for security group firewall rules
    • Azure - Missing machine error for deployed machines
    • ComputeViewServiceTest.testSearchComputesByProjectName is unstable
    • Fix testValidateEndpoint_certificate failure
    • Exclude log4j-slf4j-impl from vrops dependencies
  • vRealize Orchestrator (vRO)
    • VRO service fails to start because password of the root user within the container has expired.
    • Scheduling vro workflows is failing. Made the input form not refresh every time when schedule ngForm’s validity is changed.
    • vRO workflow run logs are not visible in web client
    • Update the merge plugins script in upgrade rpm job to handle snapshot plugin versions
    • Loading workflow slow for user given permission through Administration > Groups authenticated with PSC
    • Assign an imported workflow to the current user’s authorization context
    • Adding a tags variable to a configuration causes the web client to behave unexpectedly - Renamed the ’tags’ property of the catalog objects to ‘@tags’. This way configurations that have a variable with name ’tags’ won’t try to override the system tags.
    • “Resume workflow run” fails to resume in embedded 3 node vro cluster - Workflow was failing with a NPE when “Resume from failed” was enabled and one of the nodes was restarted.
    • [Horizon View plugin] Fix NPE for empty value LdapUser/LdapGroup in Web Client workflow execution presentation
    • [Dynamic Types plugin] is updated to v1.3.5 version to get accumulated fixes
    • Other misc fixes
  • Virtual Appliance/Clustering
    • Improve upgrade code to handle CAPSLOCKed hostnames
    • Improve LB health-checks for VA nodes to report correctly
    • Improve database failover reliability
    • Disable the docker0 interface to allow vRA deployments in 172.x.x networks
  • vRealize CodeStream
    • Nodes are currently not available. Service not yet ready." Errors while executing the Pipelines in vRA on-prem
    • Dollar resolution does not work for rollback pipelines
    • Unable to resolve Custom Integration task outputProperties via variable binding
    • CodeStream Poll task fails to report the capture request in vRSLCM while Postman reports the correct status

See Also


Get Notified of Future Posts

Follow Me

LinkedIn Icon
Twitter/X Icon
Threads Icon
RSS Icon

Recent Posts