vRealize Automation XaaS requests creating custom resource objects are delayed before completion

Products

• VMware Aria Suite

Issue/Introduction

Symptoms:

• A catalog item request in vRealize Automation based on a vRealize Orchestrator workflow which creates a custom resource object completes 2-3 minutes after the workflow has completed in Orchestrator.

Environment

VMware vRealize Automation 8.x

Cause

This delay is caused by the polling mechanism leveraged by the gateway service instead of notify blueprint service on completion it passively waits on the blueprint service to periodically request an update on the status of the workflow.

 

 

Resolution

The issue resolved in the upcoming vRealize Automation 8.11.2 release

Workaround:
To avoid the delay add the custom resource to the template directly in vRealize Automation.

Additional Information

Impact/Risks:

Xaas deployments can be delayed by a number of minutes before being marked as completed.