-
Notifications
You must be signed in to change notification settings - Fork 9.6k
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
ignore_changes: diffs didn't match during apply #6446
Comments
OK, I've made my source files a lot smaller and this is good enough to do it (I can probably get it even smaller but it's the end of my day right now). I can create this successfully, but then if I change user_data and run apply again, I get the diff mismatch error. Then I run it again and it works. (I haven't tried it without our wrapper script that does remote state, will try to do that later.)
When I delete the ignore_changes, it's OK. |
And this is with master, built at c8928e4. |
OK, here's entirely stripped down, built at c8928e4. This uses a capacity-zero ASG so it starts up fast! A single tf file (with an AWS profile called dev):
Run it, change user_data, run again:
|
Thanks for providing the solid repro case @glasser! Digging into this now. |
Just confirmed that this is fixed in v0.7.0. Thanks again for the clear report! |
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. |
I got this with
terraform apply
. It happens moderately often on this ASG.We are running TF from a relatively recent master with a couple (presumably irrelevant) local changes: meteor@4df071f
I have not been able to minimize this. This seems to only affect this ASG even though we have others; the most obvious difference is that this ASG has aws_autoscaling_policy and aws_cloudwatch_metric_alarm on it and the others don't.
The text was updated successfully, but these errors were encountered: