AWS Route53 record fails to apply when instance is stopped / shutdown

[hashibot]

This issue was originally opened by @bmalynovytch as hashicorp/terraform#6770. It was migrated here as part of the provider split. The original body of the issue is below.

---

Dear all,

I'm facing a recurrent issue.
When applying configuration with some AWS instances that are shutdown / stopped, with Route53 records attached, Terraform tries to apply a new (empty) value to the aws_route53_record which fails:

~ aws_route53_record.myhost
    records.0:         "" => ""
    records.200629859: "1.2.3.4" => ""

* aws_route53_record.myhost: InvalidChangeBatch: Invalid Resource Record: FATAL problem: ARRDATAIllegalIPv4Address (Value is not a valid IPv4 address) encountered with ''
    status code: 400, request id: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxx

Terraform Version

$ terraform -v
Terraform v0.6.16

Affected Resource(s)

• aws_route53_record

Expected Behavior

Do not apply a new value if it does not match the validation pattern.

Actual Behavior

Request fails, trying to apply an invalid (empty) value.

Steps to Reproduce

1. define a resource of type aws_instance
2. define a resource of type aws_route53_record of type A, using the previously created instance's gathered IP address (aws_instance.myhost.public_ip)
3. terraform apply
4. Instance is created, DNS record is created with the corresponding IP address
5. Stop the instance using AWS Console
6. terraform apply
7. Apply fails, trying to change/update the attached IP address

References

This issue is related to comment hashicorp/terraform#1579 (comment)

[ezyang]

Also affected by this issue. We wouldn't mind if it goes to something bogus IP in this case. Is there any good workaround for this?

[andrew-j-price]

Hopefully you found an answer by now @ezyang but my workaround is to use coalesce to set a dummy value.

resource "aws_route53_record" "microk8s_record" {
  count   = "${var.enable_microk8s}"
  zone_id = "${var.aws_route53_zone_id}"
  name    = "micro.example.com"
  type    = "A"
  ttl     = "150"
  records = ["${coalesce(aws_instance.microk8s_aio.public_ip, var.dummy_ip)}"]
}

[ezyang]

Thank you, that is a good workaround. (I worked around it by not shutting off instances lol) Excerpts from andrew-j-price's message of 2019-05-27 20:10:26 -0700:

…

Hopefully you found an answer by now @ezyang but my workaround is to use `coalesce` to set a dummy value. ``` resource "aws_route53_record" "microk8s_record" { count = "${var.enable_microk8s}" zone_id = "${var.aws_route53_zone_id}" name = "micro.example.com" type = "A" ttl = "150" records = ["${coalesce(aws_instance.microk8s_aio.public_ip, var.dummy_ip)}"] } ```

[github-actions]

Marking this issue as stale due to inactivity. This helps our maintainers find and focus on the active issues. If this issue receives no comments in the next 30 days it will automatically be closed. Maintainers can also remove the stale label.

If this issue was automatically closed and you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thank you!

[github-actions]

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.