-
Notifications
You must be signed in to change notification settings - Fork 31
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Retry "AnotherOperationInProgress" error messages #903
Comments
@sam-cogan we'll take a look at this. In the meantime, if you create a |
@infin8x thanks, I have done that and it does indeed work around the issue. |
While this workaround works perfectly the chaining of dependencies forces the developer to create the whole VNET and its Subnets in one module which is not optimal especially when trying to split code into different modules. One example might be that the code for a specific module should create the Subnet in the VNET add the corresponding resources and configure firewall rules. |
@mikhailshilkov @infin8x I would also love to hear what is the impact of deleting the first subnet only (e.g. replacing its name) after the chaining is done. e.g. What happens if in the case the Subnet 1 name has been changed? |
I think the answer is yes, unfortunately. In that case you'd have to remove all the |
Hi team, are there any plans to fix this? Terraform also had the same kind of race condition, but they already fixed that a while back. |
Hello Team, |
I'm also running into this issue so a fix would be great, Alan |
We just noticed this problem. If you need any help with this, I am more that willing! |
Any updates on this issue? It's really unfortunate to have this awkward limitation, especially when Pulumi is being deployed via CI/CD and I don't feel like chaning depends is a viable option. |
I'm getting it when trying to deploy a webapp. It deployed the rest of the stack ok, but keeps failing on this webapp, even though its the ONLY thing being deployed! I've waited 10-15 minutes from the first attempt. its my first time using Pulumi so possibly I am doing something wrong:
getting:
azure-native:web:WebApp (functionApp): |
Affected feature
Currently if Azure generates a "AnotherOperationInProgress" error Pulumi will fail. This error is often caused by trying to access two sub-resources on a resource at the same time. A good example is creating multiple subnets on a virtual network. Pulumi will try and create them all that the same time, but Azure can only create them one at a time.
Adding a back-off and retry for the "AnotherOperationInProgress" error message would help workaround this problem
The text was updated successfully, but these errors were encountered: