terraform-provider-digitalocean: Multiple digitalocean_record: 500 Server was unable to give you a response.

Terraform Version

Terraform v0.11.11
+ provider.digitalocean v1.1.0
+ provider.google v2.3.0

Affected Resource(s)

digitalocean_record

Terraform Configuration Files

// blindcut-vpn.com
resource "digitalocean_domain" "default" {
  name         = "example.com"
}

// Monitoring
resource "digitalocean_record" "test" {
  domain = "${digitalocean_domain.default.name}"
  type   = "A"
  name   = "test"
  value  = "10.10.10.10"
}

Expected Behavior

Plan: x to add, x to change, x to destroy.

Do you want to perform these actions?
  Terraform will perform the actions described above.
  Only 'yes' will be accepted to approve.

  Enter a value: yes

Actual Behavior

Error: Error refreshing state: 1 error(s) occurred:

* digitalocean_record.test: 1 error(s) occurred:

* digitalocean_record.test: digitalocean_record.test: GET https://api.digitalocean.com/v2/domains/blindcut-vpn.com/records/xxxxxxxx: 500 Server was unable to give you a response.

Sometimes it’s just one record, sometimes there are 2 or 3 records that throw the error 500. Each run is usually a different record and a different amount.

Steps to Reproduce

Create about 25 records and 1 domain
terraform apply

About this issue

Original URL
State: closed
Created 5 years ago
Comments: 20 (8 by maintainers)

Most upvoted comments

@MarianoRD @glynnforrest thanks for reporting and apologies for the inconvenience this may have caused. Looks like the team is aware of an issue here on our end (not related to Terrafrom at the moment). Will update when I have more info.

eddiezane on Apr 4, 2019

Everything seems to be working fine here, and has been working fine the last couple of weeks. Thanks for everything @eddiezane

MarianoRD on Jul 24, 2019

Hey guys, I’ve just hit this issue today having to do a terraform plan about 3 or 4 times before it finally stopped throwing errors for Digital Ocean resources. The only difference is I’m not getting a 500 status code but a 503 Service is currently unavailable. The versions I am using are;

Terraform v0.11.13
provider.digitalocean v1.2.0

The errors that I was getting are;

* digitalocean_record.wildcard_glean_sonocent_dev: digitalocean_record.wildcard_glean_sonocent_dev: GET https://api.digitalocean.com/v2/domains/sonocent.dev/records/70336309: 503 Service is currently unavailable.
* digitalocean_domain.staging_sonocent_dev: 1 error(s) occurred:

* digitalocean_domain.staging_sonocent_dev: digitalocean_domain.staging_sonocent_dev: Error retrieving domain: GET https://api.digitalocean.com/v2/domains/staging.sonocent.dev: 503 Service is currently unavailable.
* digitalocean_domain.dev_sonocent_com: 1 error(s) occurred:

* digitalocean_domain.dev_sonocent_com: digitalocean_domain.dev_sonocent_com: Error retrieving domain: GET https://api.digitalocean.com/v2/domains/dev.sonocent.com: 503 Service is currently unavailable.
* digitalocean_domain.dev_sonocent_dev: 1 error(s) occurred:

* digitalocean_domain.dev_sonocent_dev: digitalocean_domain.dev_sonocent_dev: Error retrieving domain: GET https://api.digitalocean.com/v2/domains/dev.sonocent.dev: 503 Service is currently unavailable.

StevenMilne-Sonocent on May 8, 2019

…and now it’s happening again. Repeated 500 errors every terraform apply that we attempt. Another ☁️ 🔥 ?

ghost on Apr 26, 2019

This is not fixed as of today. I’ve got a config using 22 digitalocean_record resources and it has basically become unusable. terraform apply bombs out 9 times out of 10.

My relevant versions are:

Terraform v0.11.13
+ provider.digitalocean v1.1.0

ghost on Apr 10, 2019