-
Notifications
You must be signed in to change notification settings - Fork 9.3k
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
panic: runtime error: invalid memory address or nil pointer dereference #1349
Comments
I can confirm I'm having this problem too and my steps to reproduce were nearly identical:
I'm too am also using remote S3 state as well as locks in DynamoDB. Out of the three sets of templates I have I can only reproduce the crash in one. I'm going to see if I can narrow down exactly how this is happening. |
See updated comment below.
|
So to try and figure this out, I did the following:
And it works. I guess the change I referenced above, which fixes hashicorp/terraform#15706, is not deployed yet? I'm unfamiliar with Terraform's plugin infrastructure still so I'm not sure if the above is a reasonable work around and if it's actually pointing out that the problem is fixed just not 'deployed'. |
#1316 has been merged but you won't see the fix until the next version of the AWS provider is released (version 0.1.4). |
@joshuaspence do you know when that release will be? |
I don't, sorry. That would be a question for one of the maintainers. |
Duplicate of #1314 |
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 feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thanks! |
Terraform Version
0.10.0
Affected Resource(s)
I'm not 100% sure. I did a
terraform plan
after the upgrade (and aterraform init
as per the upgrade instructions) and the crash happened. I think it may be related to remote S3 state?Debug Output
Debug Output
Panic Output
crash.log
Expected Behavior
terraform plan
should have run as expectedActual Behavior
Terraform crashed
Steps to Reproduce
terraform apply
after upgrading to 0.10.0 with remote s3 stateThe text was updated successfully, but these errors were encountered: