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

[Bug]: Error When Adding Tags on Elasticache Replication Group #40948

Open
evan-cleary opened this issue Jan 15, 2025 · 2 comments
Open

[Bug]: Error When Adding Tags on Elasticache Replication Group #40948

evan-cleary opened this issue Jan 15, 2025 · 2 comments
Labels
bug Addresses a defect in current functionality. service/elasticache Issues and PRs that pertain to the elasticache service.

Comments

@evan-cleary
Copy link
Contributor

evan-cleary commented Jan 15, 2025

Terraform Core Version

1.10.4, 1.6.6, 1.4.6

AWS Provider Version

5.83.1

Affected Resource(s)

  • aws_elasticache_replication_group

Expected Behavior

Terraform should wait for cluster to return to available state after adding the new tag before attempting to list tags

Actual Behavior

Terraform errors saying cluster is not in available state

Relevant Error/Panic Output Snippet

Error: listing tags for ElastiCache Replication Group (...): operation error ElastiCache: ListTagsForResource, https response error StatusCode: 400, RequestID: ..., InvalidReplicationGroupState: Cluster not in available state to perform tagging operations.

Terraform Configuration Files

https://gist.github.com/evan-cleary/0af2189042b92cfa9f24fac53c3a07dd

Steps to Reproduce

  1. Take supplied configuration and run terraform apply -auto-approve
  2. Wait for apply to complete
  3. Run terraform apply -auto-approve -var add_tag=true
  4. Code will error after applying tag

Debug Output

debug.gpg.log

Panic Output

No response

Important Factoids

  1. This only happens when adding a tag new
  2. Appears to be regression of [Bug]: InvalidReplicationGroupState: Cluster not in available state to perform tagging operations #30444

References

#30444

Would you like to implement a fix?

None

@evan-cleary evan-cleary added the bug Addresses a defect in current functionality. label Jan 15, 2025
Copy link

Community Note

Voting for Prioritization

  • Please vote on this issue by adding a 👍 reaction to the original post to help the community and maintainers prioritize this request.
  • Please see our prioritization guide for information on how we prioritize.
  • 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.

Volunteering to Work on This Issue

  • If you are interested in working on this issue, please leave a comment.
  • If this would be your first contribution, please review the contribution guide.

@github-actions github-actions bot added service/elasticache Issues and PRs that pertain to the elasticache service. needs-triage Waiting for first response or review from a maintainer. labels Jan 15, 2025
@justinretzolk
Copy link
Member

Related #35952

@justinretzolk justinretzolk removed the needs-triage Waiting for first response or review from a maintainer. label Jan 16, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Addresses a defect in current functionality. service/elasticache Issues and PRs that pertain to the elasticache service.
Projects
None yet
Development

No branches or pull requests

2 participants