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

diffs didn't match during apply for aws_ecs_service #3779

Closed
davedash opened this issue Nov 5, 2015 · 11 comments
Closed

diffs didn't match during apply for aws_ecs_service #3779

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

Comments

@davedash
Copy link
Contributor

davedash commented Nov 5, 2015

Error applying plan:

3 error(s) occurred:

* aws_ecs_service.REDACTED-poller-service: diffs didn't match during apply. This is a bug with Terraform and should be reported.
* aws_ecs_service.REDACTED-poller-service: diffs didn't match during apply. This is a bug with Terraform and should be reported.
* aws_ecs_service.REDACTED-poller-service: diffs didn't match during apply. This is a bug with Terraform and should be reported.

This is inside a module that's being called three times (three different environments).

/cc @hahuang65

@radeksimko
Copy link
Member

Thanks for the report, isn't this a duplicate to #3787 (comment) ? Providing a full debug log (minus any secrets) would help here.

@radeksimko radeksimko added bug provider/aws waiting-response An issue/pull request is waiting for a response from the community labels Nov 7, 2015
@davedash
Copy link
Contributor Author

davedash commented Nov 9, 2015

@radeksimko I can't tell if it's a duplicate or not. Can I email this to you? I scrubbed the log, but just in case I missed something, I'd rather just limit it's exposure.

@radeksimko
Copy link
Member

@daveadams feel free to use the email from my Github profile. If you want, you can also encrypt the message using my pubkey from https://keybase.io/radeksimko

@radeksimko
Copy link
Member

@davedash friendly ping

It would be helpful if we knew more details behind these errors, so we can more easily figure out how to fix it.

@davedash
Copy link
Contributor Author

davedash commented Dec 9, 2015

Thanks for keeping this open. I was hoping that I'd be able to reproduce
it since I did some workaround to fix it this time. If it reoccurs I'll
recreate the issue, or reopen this if you decide to close it.

On Tue, Dec 8, 2015 at 3:01 PM Radek Simko [email protected] wrote:

@davedash https://github.com/davedash friendly ping

It would be helpful if we knew more details behind these errors, so we can
more easily figure out how to fix it.


Reply to this email directly or view it on GitHub
#3779 (comment)
.

@catsby
Copy link
Contributor

catsby commented Dec 9, 2015

Thanks for the report @davedash and thanks for the triage/work @radeksimko – let's close this for now. If you can reproduce this still we'll take another look. I'm also on keybase.io, should you need to email me https://keybase.io/catsby securely

@catsby catsby closed this as completed Dec 9, 2015
@davedash
Copy link
Contributor Author

@catsby of course just after closing it does it reoccur. Sent you an email

@davedash
Copy link
Contributor Author

So I think it has to do with:

  lifecycle {
    ignore_changes =["task_definition"]
  }

@davedash
Copy link
Contributor Author

Removing it seemed to be a-ok

@scalp42
Copy link
Contributor

scalp42 commented Dec 17, 2015

Same issue on autoscaling groups here, if you try to ignore changes for desired for example, you get the same error.

@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

4 participants