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

Crash - aws provider nil pointer #3953

Closed
ryanmcnamara opened this issue Mar 28, 2018 · 7 comments
Closed

Crash - aws provider nil pointer #3953

ryanmcnamara opened this issue Mar 28, 2018 · 7 comments
Labels
bug Addresses a defect in current functionality. crash Results from or addresses a Terraform crash or kernel panic. service/elbv2 Issues and PRs that pertain to the elbv2 service.
Milestone

Comments

@ryanmcnamara
Copy link

Terraform Version

0.10.7

I had a plan fail with this message at the end of STDOUT

!!!!!!!!!!!!!!!!!!!!!!!!!!! TERRAFORM CRASH !!!!!!!!!!!!!!!!!!!!!!!!!!!!

Terraform crashed! This is always indicative of a bug within Terraform.
A crash log has been placed at "crash.log" relative to your current
working directory. It would be immensely helpful if you could please
report the crash with Terraform[1] so that we can fix this.

When reporting bugs, please include your terraform version. That
information is available on the first line of crash.log. You can also
get it by running 'terraform --version' on the command line.

[1]: https://github.com/hashicorp/terraform/issues

!!!!!!!!!!!!!!!!!!!!!!!!!!! TERRAFORM CRASH !!!!!!!!!!!!!!!!!!!!!!!!!!!!

Here is an excerpt that contains the nil pointer:
https://gist.github.com/ryanmcnamara/90dfe7f1230e25d5be2be2a4b7c0e572

I have the full output from the plan which I could direct message to someone on behalf of terraform

@vancluever vancluever added bug Addresses a defect in current functionality. crash Results from or addresses a Terraform crash or kernel panic. labels Mar 28, 2018
@bflad bflad added the service/elbv2 Issues and PRs that pertain to the elbv2 service. label Mar 28, 2018
@bflad bflad added this to the v1.13.0 milestone Mar 28, 2018
@bflad
Copy link
Contributor

bflad commented Mar 28, 2018

Hi @ryanmcnamara! 👋 Sorry you ran into trouble here. We actually just patched a fix for this into master via #3954 which will release with v1.13.0 of the AWS provider and is planned to ship next week. Given that I'm going to go ahead and close this issue.

Was your configuration running in sa-east-1 by chance?

@bflad bflad closed this as completed Mar 28, 2018
@leon-g-xu
Copy link

leon-g-xu commented Mar 28, 2018

@bflad I think we hit this issue on us-east-1

@bflad bflad mentioned this issue Mar 28, 2018
@bflad
Copy link
Contributor

bflad commented Mar 28, 2018

I can confirm v1.12.0 now crashes in us-east-1 myself but still not us-west-2. My guess is that they are rolling a service update out by region. We might need to push out v1.13.0 a little early. 😅

@eedgar
Copy link

eedgar commented Mar 28, 2018

We have run into this as well.

@cmvelo
Copy link

cmvelo commented Mar 28, 2018

Also running into this issue which is severely impeding our infrastructure rollout 👎 😢 — hopefully v1.13.0 can rollout earlier than next week.

@bflad
Copy link
Contributor

bflad commented Mar 28, 2018

Please don't be alarmed, but locking this issue to focus everyone to the original report #3949. The fix is in master and we likely are going to release v1.13.0 immediately.

@hashicorp hashicorp locked as resolved and limited conversation to collaborators Mar 28, 2018
@bflad
Copy link
Contributor

bflad commented Mar 29, 2018

This has been released in version 1.13.0 of the AWS provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Addresses a defect in current functionality. crash Results from or addresses a Terraform crash or kernel panic. service/elbv2 Issues and PRs that pertain to the elbv2 service.
Projects
None yet
Development

No branches or pull requests

6 participants