[Bug]: elasticache/replication_group update is not waiting for replication group in the available state before updating the tags

[yogesh2580]

Potentially Related

• elasticache/replication_group update is not waiting for replication group in the available state before updating the tags #23219
• resource/aws_elasticache_replication_group: Must be in available state before modifying tags #24021
• Tech debt: Reduce tags boilerplate code - PoC #29838
• [Bug]: InvalidReplicationGroupState: Cluster not in available state to perform tagging operations #30444
• [Bug]: Elasticache eventual consistency causing crash on applying new tags #31819
• [Bug]: elasticache/replication_group update is not waiting for replication group in the available state before updating the tags #33859

Terraform Core Version

1.5.4

AWS Provider Version

5.11.0

Affected Resource(s)

aws_elasticache_replication_group

Expected Behavior

The Tags on existing replication_group should be updated with the new keys-values and engine version update to 6.0.5

Actual Behavior

 Error: listing tags for ElastiCache Replication Group (arn): InvalidReplicationGroupState: Cluster not in available state to perform tagging operations.
status code: 400, request id: 5222cf25-276d-4294-8460-dd4364433d5f

Relevant Error/Panic Output Snippet

No response

Terraform Configuration Files

provider "aws" {
  shared_credentials_file = "CREDENTIAL_FILE"
  profile                 = "AWS_PROFILE"
  region                  = "us-east-1"
}

resource "aws_elasticache_replication_group" "test-redis" {
  replication_group_id          = "test-redis"
  replication_group_description = "test-redis"
  node_type                     = "cache.t4g.micro"
  engine                        = "redis"
  engine_version                = "6.0.5"
  parameter_group_name          = "parameter-grp"
  port                          = 6379
  number_cache_clusters         = 1 
  automatic_failover_enabled    = false

  security_group_ids = ["${var.redis-sg}"]
  subnet_group_name  = "${aws_elasticache_subnet_group.default.name}"

  tags {
    Name        = "TestRedis"
    Environment = "Dev"
    creator = "yogesh"  # adding new tag tagone to the existing resource group
  }
}

resource "aws_elasticache_subnet_group" "default" {
  name       = "test-subnet"
  subnet_ids = ["SUBNET-ID1", "SUBNET-ID2"]
}

Steps to Reproduce

terraform apply
Update aws_elasticache_replication_group tags
terraform apply

Debug Output

No response

Panic Output

No response

Important Factoids

No response

References

Previously the same issue was seen in version 3.74.1 and i got fixed in 4.9.0
Reference ticket number #23219

Would you like to implement a fix?

None

[github-actions]

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.

[phene]

Looks like someone attempted to fix this in the past: #24021

[ybulakhau]

I have the same behavior in version 5.31.0

[brunofarina]

Hi,
I'm having the same error when I try to update something of an existent replication group, for instance updating the engine version or even enabling the multi-az.

[github-actions]

This functionality has been released in v5.41.0 of the Terraform AWS Provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading.

For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. 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.