Change on port does not follow lifecycle of services

[cordoval]

after updating the port mappings on my task definition and changed the port for my elb then i get this error after a terraform apply even though terraform plan passed.

* aws_ecs_service.test-http: InvalidParameterException: The container test-http did not have a container port 3333 defined.
    status code: 400, request id: 31637559-9e1d-11e5-af18-8d60ba3f3e52

[catsby]

Hey @cordoval – do you by chance have an example config that I could use to reproduce this? What did the plan phase show, did it correctly show a change in both the ELB and the Task Definition?

[cordoval]

@catsby I grabbed https://github.com/alex/ecs-terraform and just change the port mappings on the .json file for the task definition. Plan passes but fails on apply.

[yissachar]

I am seeing this issue as well. I'm forced to create a new service if I want to change the port numbers on the container.

[radeksimko]

Reproduced, see #4366

[ghost]

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.