This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(121.6, 12%, 21%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EPP%3C/text%3E%3C/svg%3E)
We are Creating 3 VNets(in same region) and trying to create peering between these. Bicep code is written in such a way that these VNETS/Peering are created in parallel. VNETS are getting created (alongwith subnets as described in the code),however peering is getting failed with the error ""Cannot proceed with operation because resource XXXXXXXX used by resource XXXXXXX is not in Succeeded state. Resource is in Updating state and the last operation that updated/is updating the resource is PutVirtualNetworkOperation."
We assume this is because for VNET1 the peering status is in "Updating" state and when peering is trying to happen because of this state its failing from other 2 VNETS. We tried with "dependson" but didnt help.
How to update the bicep code in such a way that deployment should wait for sometime (or) to check for a conditon where peering status is "initiated" (or) retry after sometime before actually the main.bicep file gets into failed state.Any other solutions to resolve our issue?
Thanks in advance.
Hello @Pradeep Patlolla ,
Welcome to Microsoft Q&A Platform. Thank you for reaching out & hope you are doing well.
Could you please check if the answer provided in the below GitHub issue helps?
https://github.com/Azure/bicep/discussions/7623
If it doesn't, could you please share your Bicep code (with and without dependsOn property)?
Regards,
Gita
Thanks for your response. I have my main.bicep which creates 3VNETS & Subnets using for loop. Also within the same main.bicep i have another resource to create VNET peering(uses for loop) between above created VNETS .
At the time of peering since the VNETS are not fully created peering is getting failed(tried with depends on & batchsize as well).I will try the suggested option and unable to share the bicep code.Please suggest for any other options to delay certain modules within my main.bicep code so that resources are fully created and then the next module will kickstart.
One other observation is, if we run the deployment for second time everything is working fine and also peering is getting established.Our goal is to create everything on the first deployment itself.
Thanks in advance,
Pradeep Reddy Patlolla
I was able to resolve the issue. Resolution was to remove the VNet peering resource from main.bicep and calling it as a module instead with dependency on VNet's. Hope it might help someone.
Thanks,
Pradeep Reddy Patlolla
Hello @Pradeep Patlolla ,
Thank you for the update and sharing the resolution. Glad to hear that you were able to fix the issue.
I've converted your comment to an answer for better visibility as this can be beneficial to other community members.
Regards,
Gita