-
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
Terraform Crash v0.12.2 #21896
Comments
I just had a similar problem, which I was able to solve. The main hint was that on the I was doing some tests with the As in the next execution terraform created a new instance (without destroying the previously created one) I manually deleted the instance that was previously created. Then, IIRC, I deleted a instance before executing After some digging into the terraform state file I realized that terraform still had some pointers to two instances that I deleted previously (at this point I had no more instances running on AWS). But on the output section I had a pointer to instance After deleting the references to instance My terraform version was Hope that this at least help someone with a similar issue. |
Fix for a crash during terraform plan: If there is a multi-instance resource (count > 1) where one of the instances was deleted in the deployment but was still present in the terraform state, getResourceInstancesAll crashed. Check not only for rs.Instances[key] to exist, but also to have a valid Current pointer.
I created a pull request that should fix this issue. |
closed by #21979 |
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. |
Hi,
Terraform crashed for the first time for my project of an ECS cluster. I'm using the v0.12.2
This is the last part of the crash.log :
Thanks for your help.
The text was updated successfully, but these errors were encountered: