Status=429 Code="RetryableError" Message="A retryable error occured." #7986
Comments
|
This occurs on more deployments than it doesn't. In fact, it's bad enough that I'm ignoring the return value from |
|
cc: @stack72 I'm still getting this on Is there a proper dependency between the NSG and Subnet established in the Terraform plan? One needs to wait on the other to finish provisioning. |
|
I also get these, have to retry everytime: It seems it tries to create the NICs before the subnets are ready, probably because it is applying a security group or route table. Terraform v0.7.4 |
|
Just tried with v0.7.8, still have to retry the apply: |
|
Yep, I'm constantly seeing 429s in 0.7.8 as well (without additional detail, so assuming they are rate limits?) This is after trying For me at least, additional attempts at What I do not understand is that I should note too that my .tf is just a rip of the example/test one in the docs, so I'm reasonably sure the dependencies etc. are correct |
|
This is the output when I have TF_LOG set to debug: Does 'GatewayError' point to a different problem here? (I can't see anything that implies I can change/resolve with diff. options etc. though?) Seems to connect it back to #7153 (comment) perhaps? |
|
@DavidR91 Yes, "GatewayError" indicates it's different. If you start from a fresh tfstate and change the resource group you're deploying to, do you still get the same error? If so, I can follow-up and see if there's a service incident going on. |
|
@colemickens you're absolutely right, seems to be a service problem. Trying with a new resource group worked straight away (and the old resource group took an exceptionally long time to |
|
Okay, if it's not reproing on a new run then I'm not too terribly worried about it. Feel free to follow up with Support if you want them to look into why you were getting that error reliably on that other RG -- looked like a platform issue to me anyway. |
|
Just another data point to add for this issue; I also consistently see the same behavior. |
|
I just tried with the latest master and I always get this error. Retrying fixes the issue but it seems there's some kind of dependency missing and a NIC is being created before the subnet is finished: |
|
I'm getting this sporadically on v0.8.6 for other network related resources. I think this is similar to errors Terraform has had with other providers (AWS) where Terraform just needs to handle the 429 as a 404 and retry the same operation (with backoff). |
|
I'm seeing this error on v0.9.2 when deploying a network interface that is in a specific subnet: `* azurerm_network_interface.bastion: 1 error(s) occurred:
How come this is still happening on version 0.9.2? This issue was opened in Aug 2016... Any chance this will get fixed soon? Thanks |
|
It's actually been since June. cc: @tombuildsstuff |
|
I am getting the same issue when I am trying to associate NSG to NIC _azurerm_network_interface.web-srv-interface: network.InterfacesClient#CreateOrUpdate: Failure responding to reques |
|
@colemickens @tombuildsstuff I get the same when creating network interface, if at the same time there are rules added to network security group (rendering network security group in "Updated" state). I need to retry every time as well. Here's an error.
The solution would be an auto-dependency of In short the error happens because |
|
Hi, I'am using Terraform 0.9.3 and have also the same issue
I am deploying several VM (>12) connected to many Subnet with NSG applied on Subnet. This issue occurs every time on my deployment (if i execute on more time Terraform apply, deployement can finish but it appears to me not ready for production) |
|
Hi @squasta I believe this issue has been fixed in Terraform 0.9.4 - would it be possible for you to confirm using this version? Thanks! :) |
|
Not yet for me: |
|
Hi @edevil Thanks for letting us know, apologies about this - I've taken another look at this and managed to isolate this down to creating multiple NIC's in different Subnets within the same Virtual Network at the same time in this minimal Terraform configuration as my test case. I've opened PR #14365 which I believe fixes this - and tested it using the configuration posted above, and the Terraform configuration generated from Thanks! |
|
I experienced a similar problem with LB creation. After the error occured if I run apply again the resource is created normal. When I want destroy the same behavior occurs. Follow the error
|
|
Never mind, Azure may has a rate limit on their api because when I set -parallelism=2 for example no errors occurred. |
|
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further. |
ghost
locked and limited conversation to collaborators
I think this might be related with this issue #7153 I'm open it to provide more information about it and to keep separate from that issue.
Terraform Version
Terraform v0.7.0
Affected Resource(s)
Terraform Configuration Files
link
Debug Output
link
Standard Output
Azure Error
The text was updated successfully, but these errors were encountered: