-
Notifications
You must be signed in to change notification settings - Fork 9.7k
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
Tainting ELB fails #10192
Comments
Hello! I tried your config and steps exactly and wasn't able to reproduce this error. Can you please point me in a direction to try to reproduce this? |
I am having the same issue. One particular piece to note is that the ELB definition is contained in a module, not directly in the config. I'll see if I can reproduce this regularly via taint (our error occurred when we changed the ELB's name attribute and it was forcing a re-create). |
@jangrewe Do you have any resources that use the outputs of your ELB creation that have the
I believe this may be part of my issue. We have the If I set the However I receive a notification about:
|
Thanks @jrnt30, i did have My Route53 records still get modified with every run, so tainting them and the ELBs didn't fix anything, but at least i got rid of the error now. |
Thanks all for the input, but unfortunately I still can't get a reproduction here. I do believe this error is real since it has been reported multiple times, but a clean reproduction so we can fix it still eludes us. Until we can get that, I unfortunately won't be able to do much here... I'm going to close this for now, but if someone gets a repro for this please just open a new issue and we'll get going ASAP! |
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 wanted to try if tainting the ELB helps with getting rid of #9289, but this made it only worse...
Terraform Version
0.7.11
Affected Resource(s)
Terraform Configuration Files
Error Output
Expected Behavior
The ELB should have been destroyed and recreated
Actual Behavior
The error above.
Steps to Reproduce
terraform taint aws_elb.elb
terraform apply
The text was updated successfully, but these errors were encountered: