-
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
Terraform 0.12.14 panic during show plan #23377
Comments
@BookOfGreg thanks for reporting this! Have you been able to put together a demonstration config that reproduces this issue? |
Unfortunately my boss hasn't allowed me to put time into this yet. I will provide one when I can which unfortunately might not be soon. |
Having similar issue. |
@pkolyvas what do you need? This is failing on multiple terraform projects. |
A set of HCL (preferrably small) that causes the crash as a reproduction so it can be debugged. |
I just ran into this as well on provider "aws" {
region = "eu-central-1"
}
resource "aws_vpc" "test-aws-vpc" {
cidr_block = "10.123.4.0/24"
} This is the process for me:
I was only able to reproduce it if the plan is for the VPC to be replaced. If it's added or destroyed, or both (e.g. by renaming the resource) then it seems to work. Regarding the downgrade workaround, is there any easy way for me to downgrade the state file ? Panic log:
|
@valorl thanks so much for taking the time and creating a reproducible case. Unfortunately that was our issue as well, e.g. issues happened during security-group updates (as also seen in OP's initial report) and not during adding or deleting resources. This is also why we only noticed this breaking issue after we have already upgraded projects. Which also brings us to this:
This is unfortunately not possible and completely bit us in the ass this time. We had to comment out any We are hoping, going forward, that a test-case will be implemented against this, and are patiently looking forward to a fix |
@lifeofguenter I was able to downgrade the statefile by manually changing |
This bug could be related to some changes made to + module.vpc.aws_vpc.tf-network-aws-vpc In Just thought I'd mention that in case someone knows about some PRs or commits that could be referenced here. |
I can confirm this crash for 0.12.14 and 0.12.16. Just write here to get updates on this and deliver an additional crash log. `2019/11/21 15:47:03 [INFO] Terraform version: 0.12.16 goroutine 1 [running]: |
Hey, I can confirm the same on a |
Here is a little bit of information about the changeset that is causing this .. (output from plan)
Something about this changeset is breaking it ..
|
Can we expect hotfix release? |
@Lirt No hotfix, this went out earlier today in 0.12.18. |
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
Crash Output
https://gist.github.com/BookOfGreg/97d0dca47b9e3cff5889b50d90270188
Expected Output
Actual Output
It crashes and continues to output mid-run.
Steps to Reproduce
Cannot reproduce, happened once, subsequent runs ofterraform show plan
on the same plan file did not crash.I have a plan that will crash terraform relatively consistently, I'll see if I can strip it of sensitive info for sharing.
Additional Context
Upgraded from 0.12.13 due to this bug:
#21949
0.12.13 did not crash but also did not have expected behavior for
show plan
References
The text was updated successfully, but these errors were encountered: