Hi,
its is looks very similar to that: https://knowledge.broadcom.com/external/article/314749/another-conflicting-request-is-already-i.html.
Cannot find this was fixed in 8.11.2 as promised: https://docs.vmware.com/en/vRealize-Automation/services/rn/vrealize-automation-release-notes/index.html.
PS. Technically, the final step is "Deployment resource completed". In general, I would recommend resizing the disks (or performing any hardware changes) before the first boot - in a pre-provisioned state. That's what vRA does as well, when building a VM.
Additionally, I'm always trying to incorporate a check to ensure that there are no other running tasks on the VM before the main workflow begins. If there are some tasks, it is possible to create a while loop to wait or fail the workflow, which will fail the vRA deployment. This could be related to your issue in general as well.
------------------------------
If you find the answer helpful, please click on the RECOMMEND button.
Please visit my blog to get more information:
https://www.clouddepth.com------------------------------
Original Message:
Sent: Oct 24, 2024 11:37 AM
From: DizzyMurloc
Subject: Resize VM boot disk during the compute provision phase
Hi all,
I'm trying to resize the boot disk of a VM during its creation. The disk size is defined in the template I used to clone from, but I want to modify this value based on the input provided by the user in the service catalog form.
Here's how I'm attempting to achieve this:
- I've created a workflow that executes the Day 2 operation "Resize Boot Disk" via API.
- This workflow is triggered by a compute post-provision event subscription.
The problem I'm encountering is that if I enable the "block execution of events in topic" option, the workflow fails and returns the following error from the API request:
error{"message":"Another conflicting request is already in progress.","statusCode":409,"errorCode":20009}
With this option disabled, the resize works fine, but I need to confirm that the resize completes successfully before marking the deployment as complete.
Why am I getting this error? When the compute post-provision event is triggered, isn't the VM fully created yet?
On the other hand, is there another way to achieve this? I'm sure that executing a Day 2 operation isn't the best practice for resizing the VM boot disk, there must be a better way.
I hope someone can help me.
Regards,