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

Unable to Apply a Change to ECS service #3787

Closed
brianknight10 opened this issue Nov 6, 2015 · 3 comments
Closed

Unable to Apply a Change to ECS service #3787

brianknight10 opened this issue Nov 6, 2015 · 3 comments
Labels
bug provider/aws waiting-response An issue/pull request is waiting for a response from the community

Comments

@brianknight10
Copy link

I was looking to change the container port for the ELB associated with my ECS service. I changed my aws_ecs_service task from:

resource "aws_ecs_service" "event" {
    name = "event"
    cluster = "${aws_ecs_cluster.event.id}"
    task_definition = "${aws_ecs_task_definition.event.arn}"
    desired_count = 4
    iam_role = "${terraform_remote_state.vpc.output.iam_ecs_service_role_id}"
    load_balancer {
        elb_name = "${aws_elb.event.name}"
        container_name = "event"
        container_port = 8080
    }
}

to:

resource "aws_ecs_service" "event" {
    name = "event"
    cluster = "${aws_ecs_cluster.event.id}"
    task_definition = "${aws_ecs_task_definition.event.arn}"
    desired_count = 4
    iam_role = "${terraform_remote_state.vpc.output.iam_ecs_service_role_id}"
    load_balancer {
        elb_name = "${aws_elb.event.name}"
        container_name = "event"
        container_port = 80
    }
}

After creating a plan, the applied failed with the message of: * aws_ecs_service.event: diffs didn't match during apply. This is a bug with Terraform and should be reported.

This may or may not be related to #3444. This happened on Atlas running v.0.6.6.

@radeksimko
Copy link
Member

Thanks for the report,
in case like this (diffs didn't match) it would help if you can provide the full debug log (minus any secrets, obviously). Then we'd at least know which field is causing the problem and what's the actual diff.

Since you're using terraform_remote_state, I believe this is related to #2765 .
@apparentlymart is working on a fix for all similar issues in #3060

@radeksimko radeksimko added the waiting-response An issue/pull request is waiting for a response from the community label Nov 7, 2015
@catsby
Copy link
Contributor

catsby commented Dec 9, 2015

Hey all – we haven't heard back in a while so I'm going to go ahead and close this. I suspect too that it's covered in one of the other issues referenced.

Thanks!

@catsby catsby closed this as completed Dec 9, 2015
@ghost
Copy link

ghost commented Apr 29, 2020

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.

@ghost ghost locked and limited conversation to collaborators Apr 29, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug provider/aws waiting-response An issue/pull request is waiting for a response from the community
Projects
None yet
Development

No branches or pull requests

3 participants