terraform-provider-azurerm: Getting "Failure sending request: StatusCode=429 -- Original Error: context deadline exceeded" when running over 2000 DNS Records

Community Note

  • Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
  • Please do not leave “+1” or “me too” comments, they generate extra noise for issue followers and do not help prioritize the request
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment

Terraform (and AzureRM Provider) Version

Terraform v0.13.5 (also tried Terraform v0.14, same error)

  • provider registry.terraform.io/hashicorp/azurerm v2.39.0

Affected Resource(s)

azurerm_dns_a_record azurerm_dns_cname_record

Terraform Configuration Files

The A and CNAME records are very similar to what is below except that are over 1000 records for each

provider "azurerm" {
#    version="2.39"
    features {}
}

resource "azurerm_resource_group" "example" {
  name     = "large-rg"
  location = "West US"
}

resource "azurerm_dns_zone" "example" {
  name                = "dnsrecords.com"
  resource_group_name = azurerm_resource_group.example.name
}

resource "azurerm_dns_a_record" "arecord" {
        name                = " arecord "
        zone_name           = " dnsrecords.com"
        resource_group_name = "large-rg"
        ttl                 = 300
        records             = ["1.1.1.1"]
}

resource "azurerm_dns_cname_record" "cname" {
        name                = "cname"
        zone_name           = " dnsrecords.com"
        resource_group_name = "large-rg"
        ttl                 = 300
        record              = "testing.trafficmanager.net."
}

Debug Output

2020/12/09 17:11:22 [TRACE] eval: *terraform.EvalWriteState 2020/12/09 17:11:22 [TRACE] EvalWriteState: recording 1 dependencies for azurerm_dns_zone.example 2020/12/09 17:11:22 [TRACE] EvalWriteState: writing current state object for azurerm_dns_zone.example 2020/12/09 17:11:22 [TRACE] [walkRefresh] Exiting eval tree: azurerm_dns_zone.example 2020/12/09 17:11:22 [TRACE] vertex "azurerm_dns_zone.example": visit complete 2020/12/09 17:11:22 [TRACE] vertex "azurerm_dns_zone.example": dynamic subgraph completed successfully 2020/12/09 17:11:22 [TRACE] vertex "azurerm_dns_zone.example": visit complete 2020/12/09 17:11:22 [TRACE] vertex "azurerm_dns_zone.example (expand)": dynamic subgraph completed successfully 2020/12/09 17:11:22 [TRACE] vertex "azurerm_dns_zone.example (expand)": visit complete 2020/12/09 17:11:22 [TRACE] dag/walk: upstream of "provider[\"registry.terraform.io/hashicorp/azurerm\"] (close)" errored, so skipping 2020/12/09 17:11:22 [TRACE] dag/walk: upstream of "root" errored, so skipping 2020/12/09 17:11:22 [TRACE] statemgr.Filesystem: removing lock metadata file .terraform.tfstate.lock.info 2020/12/09 17:11:22 [TRACE] statemgr.Filesystem: unlocked by closing terraform.tfstate 2020-12-09T17:11:22.725-0800 [DEBUG] plugin: plugin process exited: path=.terraform/plugins/registry.terraform.io/hashicorp/azurerm/2.39.0/windows_amd64/terraform-provider-azurerm_v2.39.0_x5.exe pid=18812 2020-12-09T17:11:22.725-0800 [DEBUG] plugin: plugin exited

Panic Output

Expected Behaviour

Should be able to generate the 2000+ A and CNAME records

Actual Behaviour

Getting “dns.RecordSetsClient#Get: Failure sending request: StatusCode=429 – Original Error: context deadline exceeded” when running terraform apply

Steps to Reproduce

terraform apply

About this issue

  • Original URL
  • State: closed
  • Created 4 years ago
  • Reactions: 8
  • Comments: 15

Most upvoted comments

Whatever it is it was introduced with the Terraform Azure provider 2.x versions from the very beginning. We could reproduce it with version 2.1.0. So, I assume that this exists since version 2.0.0.

Terraform Azure provider version 1.44.0 just works.