Skip to content
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

Terraform AWS Route53: can't update record identifier #19646

Closed
dtanasienko opened this issue Jun 3, 2021 · 6 comments
Closed

Terraform AWS Route53: can't update record identifier #19646

dtanasienko opened this issue Jun 3, 2021 · 6 comments
Assignees
Labels
bug Addresses a defect in current functionality. service/route53 Issues and PRs that pertain to the route53 service.

Comments

@dtanasienko
Copy link

dtanasienko commented Jun 3, 2021

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 other comments that do not add relevant new information or questions, 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 CLI and Terraform AWS Provider Version

Terraform v0.15.5
on linux_amd64
+ provider registry.terraform.io/hashicorp/aws v3.43.0

Affected Resource(s)

  • aws_route53_record

Terraform Configuration Files

variable "ip" {}
variable "aws_region" {}
variable "aws_access_key" {}
variable "aws_secret_key" {}

provider "aws" {
  region = var.aws_region
  access_key = var.aws_access_key
  secret_key = var.aws_secret_key
}

data "aws_route53_zone" "selected_zone" {
  name = "<aws-zone>."
}

resource "aws_route53_record" "multivalue_answer_routing_policy_records" {
  zone_id = data.aws_route53_zone.selected_zone.zone_id
  name = "test.<aws-zone>"
  type = "A"
  ttl = "5"

  multivalue_answer_routing_policy = true
  set_identifier  = "aaa-${var.ip}"
  records = [var.ip]
}

Debug Output

https://gist.github.com/dtanasienko/3dca074a2e55e8b7b86fe0bea1ffaf08

Expected Behavior

DNS record identifier updated successfully.

Actual Behavior

The update failed. The next time you run terraform apply, a new DNS record will be created.

Steps to Reproduce

  1. terraform apply
  2. terraform apply with new identifier
@github-actions github-actions bot added needs-triage Waiting for first response or review from a maintainer. service/route53 Issues and PRs that pertain to the route53 service. labels Jun 3, 2021
@gdavison
Copy link
Contributor

gdavison commented Jun 5, 2021

Thanks for raising this issue, @dtanasienko. Could you please run the update with debug logging enabled? To do so, see the instructions at https://www.terraform.io/docs/internals/debugging.html

@gdavison gdavison added the waiting-response Maintainers are waiting on response from community or contributor. label Jun 5, 2021
@gdavison gdavison self-assigned this Jun 5, 2021
@dtanasienko
Copy link
Author

@breathingdust breathingdust added bug Addresses a defect in current functionality. and removed needs-triage Waiting for first response or review from a maintainer. labels Aug 31, 2021
@handlerbot
Copy link
Contributor

@dtanasienko I think this is a duplicate of #7998; I have just submitted a PR there to fix that issue. Do you want to check if this issue is a duplicate and close, if so?

@github-actions github-actions bot removed the waiting-response Maintainers are waiting on response from community or contributor. label Jun 30, 2022
@dtanasienko
Copy link
Author

@handlerbot Hi, this is a duplicate of #7998. We can close it. Thanks!

@handlerbot
Copy link
Contributor

@dtanasienko I'm not an admin on this repository, so I can't close issues; I just wrote the code to fix the bug from outside. Can you close this issue? Thanks!

@github-actions
Copy link

github-actions bot commented Aug 7, 2022

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.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Aug 7, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Addresses a defect in current functionality. service/route53 Issues and PRs that pertain to the route53 service.
Projects
None yet
Development

No branches or pull requests

4 participants