Skip to content
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

VPC Peering connection Panic: invalid memory address or nil pointer dereference #8392

Closed
erutherford opened this issue Aug 22, 2016 · 4 comments

Comments

@erutherford
Copy link
Contributor

erutherford commented Aug 22, 2016

Terraform Version

0.7.1, I've confirmed that this crash doesn't occur in 0.7.0

Affected Resource(s)

  • aws_vpc_peering_connection

Terraform Configuration Files

Here's the module I'm using to setup our networking resources
https://www.dropbox.com/s/if8bwqdm4g03tz0/aws_vpc_complete.tar.gz?dl=0

Panic Output

complete crash.log file encrypted with the hashicorp pub key

https://www.dropbox.com/s/9pi8gz4r0yecfbz/terraform_crash_v0.7.1.log.gpg?dl=0

gist of the panic

https://gist.github.com/erutherford/2029aef0412ff526d7b7885b59c5bda2

Expected Behavior

In versions before 0.7.1 this module was working without an issue.

I reverted back to 0.7.0 and I'm able to run terraform plan and terraform apply without an issue.

I know there were changes made for peering options, but I'm not sure if that's related (and I don't believe I should have needed to change my config since it's defined as optional) and that the very least it should provide an error for that, not crash.

It should create the resources or leave them alone if nothing as changed.

Actual Behavior

It's crashing with a panic

Steps to Reproduce

Please list the steps required to reproduce the issue, for example:

  1. terraform plan
@stack72
Copy link
Contributor

stack72 commented Aug 22, 2016

Hi @erutherford

Thanks for reporting the issue here - we apologise this has happened. Hopefully it hasn't caused any issues for you! We are actively working on getting this fixed #8338

We hope to have that ready really soon! I am going to close this as a duplicate of #8334

Paul

@erutherford
Copy link
Contributor Author

@stack72 thanks for the update, sorry I missed the existing issue.

@stack72
Copy link
Contributor

stack72 commented Aug 22, 2016

Nothing to apologise for at all :) just easier to track in 1 place

@ghost
Copy link

ghost commented Apr 23, 2020

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.

@ghost ghost locked and limited conversation to collaborators Apr 23, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants