"Another conflicting request is already in progress.","statusCode":409," Error when submitting multiple deployment based actions

Products

• VMware Aria Suite

Issue/Introduction

Symptoms:

• Submitting a custom resource action or API request that calls out of the box actions in the workflow, for example Change Lease or Change Owner, the workflow or API request fails with the error:

{"message":"Another conflicting request is already in progress.","statusCode":409,"errorCode":20009}

•  The issue affects actions including but not limited to:

• Adding a tag
• Changing deployment lease
• Adding disk
• Set deployment CPU / RAM
• Changing owner

Environment

VMware vRealize Automation 8.x

VMware Aria Automation 8.x

Cause

Users cannot trigger two out-of-the-box, deployment-level Day-2 actions at the same time. For example, if a deployment creation is in progress, other Day-2 operations are blocked during this period.

Even when a deployment reaches the "Deployment Completed" state, the underlying request may still be in progress at the deployment level. Therefore, any additional Day-2 actions, such as "Change Owner", must be deferred until the initial request is fully completed.

Users should implement an asynchronous flow that waits for the deployment request to finish before initiating further actions.

Resolution

A resolution for this issue is scheduled to be included in the Aria Automation 8.11.2 release. This will include changes to the deployment service api to allow for synchronous submission of requests. These changes will be outlined in the Aria Automation swagger API documentation.

Workaround:
The workaround in the interim is to submit the requests asynchronously.

Additional Information

Impact/Risks:
API requests for deployment objects can only be submitted asynchronously.