-
Notifications
You must be signed in to change notification settings - Fork 9.4k
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
aws_security_group re-create: diffs didn't match during apply #2117
Comments
Hey @alexlouden – do you have a config file (minus any secrets) that demonstrates this for me? |
Hey @catsby, at the time I tried to reproduce it in a simpler example but couldn't get it to fail in the same way. I've changed companies now, so don't have access to the original config - sorry! |
I think I'm running into the same problem. Interesting thing about it, the security group that is causing the error doesn't appear in the plan at all (and shouldn't be changing). |
Hey all – I'm not able to reproduce this with that we have here, so I'm closing this for now. If you have more information that can help me debug, I'll happily dig in some more. Thanks! |
I'm still seeing this (but working around it by not changing SG names). I will try and see if I can provide an easier way to reproduce. |
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've renamed all 4 security groups, 3 of which only allow ingress from other security groups. There's one security group per instance type (e.g.
instance.worker
<==>security_group.worker
).On
terraform apply
, terraform tries to re-create the security groups, but fails with the following error:I've captured the output of
TF_LOG=1 terraform apply
and extracted (hopefully) the relevant bit:https://gist.github.com/alexlouden/58d1d364eee67d050fce
Let me know if there's any more information I can give (privately would be much easier!). I tried to reproduce with only two security groups but the same change succeeded, so there must be more to it than just ingress dependencies. Maybe related to #1877?
Thanks!
The text was updated successfully, but these errors were encountered: