-
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
Error applying in v0.10.0 - diffs didn't match during apply - attribute mismatch: availability_zones #15810
Comments
Hey @davidgenn do you by chance have a configuration that reproduces this that you could share? Please be sure not to share any secrets if you do. |
I've been experiencing this as well.
The main auto scaling group configuration looks like this:
I notice that running |
Hi, we've been experiencing the same issue using |
Also seeing this one in version https://gist.github.com/rockholla/4bf918d132f32abb73a25f8c09adf73c And related config for the auto scaling group:
|
Same issue with autoscaling group in 0.10.0, 0.10.1, 0.10.2 |
Experiencing similar issues with autoscaling group an 0.10.2 |
I have been noticing this issue (mismatched diffs for AZ on ASG) as well since 0.10.x. Second |
Same here, on 0.10.2. Trying to create an auto scaling group:
First time running apply produces this output:
Second time running apply, it works. |
Can confirm this behavior. Running apply again makes it work without any errors. |
Can confirm this issue too. Second apply works perfectly(without any other modification). If needed I can provide my configuration but it's nothing too exotic( ALB + 2 ASGs in 2 AZs). |
Remove the |
Just encountered this myself, eliminating |
Same here in Terraform v0.11.0 when creating a new auto scaling group (availability_zones is set) |
same issue with
|
I am automating updates across our business and seeing 133 of these failures. Here's one:
|
Hi all! This seems to be the same thing that we discussed over in #17263. Eventually the requester realized that using |
@apparentlymart that doesn't work either, terraform ended up picking a random subnet from a different VPC which ends up with error:
This is with terraform 0.11.3 Don't you guys have some kind of regression tests so basic things like this don't brake upon new releases? I saw posts reporting the same issue in 0.10 and 0.9 as well, how is it possible bugs like this to slip through for so long? |
Actually for that module I had commented out the |
Hi, Same issue here. |
I have hit this error too, with Terraform v0.11.7. There is a gist here with the details. I was applying a plan containing only 3 resources:
The EBS volume already existed and was not going to be destroyed, in the plan. It was only going to have some tags updated. The EC2 and the volume attachment were planned to be destroyed and recreated, because I had made some changes to the Please let me know if more context/detail is needed! |
Hello! Thanks for reporting this issue. Unfortunately the error output in this "diffs didn't match" situation is often not enough to diagnose the problem. Starting in 0.12 the situation that causes this error is more precisely reported, and the necessary debugging information is recorded in the logs. If this issue persists after upgrading Terraform, please file an issue with the referenced provider. Thanks |
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. |
Terraform Version
0.10.0
Terraform Configuration Files
NA
Debug Output
https://gist.github.com/davidgenn/31798c84e48c5b6c55151ed9c9e71fb9
Panic Output
NA
Expected Behavior
Run
terraform apply
AWS resources created.
Actual Behavior
AWS resources partially created. Diff error returned.
Steps to Reproduce
Please list the steps required to reproduce the issue, for example:
https://gist.github.com/davidgenn/3db8f6d44ca7436d0764e78fafe12f63
terraform apply
Important Factoids
This was previously working under version 0.9.11
References
NA
The text was updated successfully, but these errors were encountered: