ecs_service inconsistent apply intermittently when placement_constraints is set

[driskillb43]

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: 0.14.10
AWS Provider Version: 4.8.0

Affected Resource(s)

• aws_ecs_service

Terraform Configuration Files

data "aws_ecs_cluster" "this" {
  cluster_name = "test"
}

resource "aws_ecs_task_definition" "test_task_definition" {
  family                   = "test-service"
  network_mode             = "bridge"
  requires_compatibilities = ["EC2"]
  container_definitions = jsonencode([
    {
      essential   = true
      name        = "test-server"
      image       = "test-image"
      cpu         = 128
      memory      = 256
      environment = []
      portMappings = [
        {
          containerPort = 8000
          hostPort      = 8000
        }
      ]
    }
  ])
}

resource "aws_ecs_service" "test_service" {
  name                = "test-service"
  cluster             = data.aws_ecs_cluster.this.arn
  task_definition     = "${aws_ecs_task_definition.test_task_definition.family}:${aws_ecs_task_definition.test_task_definition.revision}"
  scheduling_strategy = "DAEMON"
  deployment_controller {
    type = "ECS"
  }
  placement_constraints {
    type       = "memberOf"
    expression = "attribute:user_data_version == 2"
  }
}

Debug Output

Not able to reproduce it with TF_LOG=TRACE set oddly.

Expected Behavior

Should apply fine

Actual Behavior

The following error is thrown intermittently:

When applying changes to aws_ecs_service.test_service, provider "registry.terraform.io/hashicorp/aws" produced an unexpected new value: Root resource was present, but now absent.

This is a bug in the provider, which should be reported in the provider's own issue tracker.

Steps to Reproduce

It requires multiple tries to hit it, it does not happen every time.

1. terraform apply

Important Factoids

If I remove the placement_constraints from the aws_ecs_service, I do not encounter the issue anymore. Also, this seems to have cropped up in the last two weeks. I was not seeing this issue a few weeks before.

References

• This is a bug in the provider, which should be reported in the provider's │ own issue tracker #23878 - Maybe related?

[github-actions]

This functionality has been released in v4.22.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.