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

Terraform Crash #13569

Closed
aqilco opened this issue Apr 12, 2017 · 3 comments
Closed

Terraform Crash #13569

aqilco opened this issue Apr 12, 2017 · 3 comments

Comments

@aqilco
Copy link

aqilco commented Apr 12, 2017

Terraform v0.9.2

Crash log attached.

crash.log.zip

During terraform destroy:

vagrant@vagrant:/vagrant/terraform.configurations/Aqilco.Cloud$ terraform destroy
Do you really want to destroy?
Terraform will delete all your managed infrastructure.
There is no undo. Only 'yes' will be accepted to confirm.

Enter a value: yes

aws_iam_group.infra_ops_group: Refreshing state... (ID: InfraOpsGroup)
aws_iam_user.infra_ops_user: Refreshing state... (ID: batman)
aws_iam_policy.infra_admin_policy: Refreshing state... (ID: arn:aws:i...inPolicy)
aws_iam_role.infra_admin_role: Refreshing state... (ID: InfraAdminRole)
aws_iam_access_key.infra_ops_user: Refreshing state... (ID: AKIAIYQSJNULTHOAHUIQ)
aws_iam_group_policy.infra_ops_group_policy: Refreshing state... (ID: InfraOpsG...upPolicy)
aws_iam_group_membership.infra_ops_group_membership: Refreshing state... (ID: infra_ops...mbership)
aws_iam_policy_attachment.infra_admin_policy_attachment_to_infra_admin_role: Refreshing state... (ID: infra_adm...tachment)
aws_instance.bender: Refreshing state... (ID: i-0bfa7721ddd4d7b79)
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x48 pc=0x99ebf6]

goroutine 213 [running]:
github.com/hashicorp/terraform/terraform.(*State).sort(0x0)
/opt/gopath/src/github.com/hashicorp/terraform/terraform/state.go:745 +0x26
github.com/hashicorp/terraform/terraform.WriteState(0x0, 0x7450720, 0xc4200fa770, 0x439075, 0xc4209c7d10)
/opt/gopath/src/github.com/hashicorp/terraform/terraform/state.go:2000 +0x40
github.com/hashicorp/terraform/state/remote.(*State).PersistState(0xc4203ea6e0, 0x0, 0x0)
/opt/gopath/src/github.com/hashicorp/terraform/state/remote/state.go:58 +0x79
github.com/hashicorp/terraform/backend/local.(*Local).opApply(0xc4202cf9a0, 0x7475da0, 0xc4203a1000, 0xc4202c64d0, 0xc420485ef0)
/opt/gopath/src/github.com/hashicorp/terraform/backend/local/backend_apply.go:138 +0x5d9
github.com/hashicorp/terraform/backend/local.(*Local).(github.com/hashicorp/terraform/backend/local.opApply)-fm(0x7475da0, 0xc4203a1000, 0xc4202c64d0, 0xc420485ef0)
/opt/gopath/src/github.com/hashicorp/terraform/backend/local/backend.go:226 +0x52
github.com/hashicorp/terraform/backend/local.(*Local).Operation.func1(0xc4202cf9a0, 0xc4203f1c60, 0xc4203f1c50, 0x7475da0, 0xc4203a1000, 0xc4202c64d0, 0xc420485ef0)
/opt/gopath/src/github.com/hashicorp/terraform/backend/local/backend.go:246 +0x9a
created by github.com/hashicorp/terraform/backend/local.(*Local).Operation
/opt/gopath/src/github.com/hashicorp/terraform/backend/local/backend.go:247 +0x192

!!!!!!!!!!!!!!!!!!!!!!!!!!! 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 Terraform1 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.

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

Hi there,

Thank you for opening an issue. Please note that we try to keep the Terraform issue tracker reserved for bug reports and feature requests. For general usage questions, please see: https://www.terraform.io/community.html.

Terraform Version

Run terraform -v to show the version. If you are not running the latest version of Terraform, please upgrade because your issue may have already been fixed.

Affected Resource(s)

Please list the resources as a list, for example:

  • aws_instance
  • dnsimple_record

If this issue appears to affect multiple resources, it may be an issue with Terraform's core, so please mention this.

Terraform Configuration Files

# Copy-paste your Terraform configurations here - for large Terraform configs,
# please use a service like Dropbox and share a link to the ZIP file. For
# security, you can also encrypt the files using our GPG public key.

Debug Output

Please provider a link to a GitHub Gist containing the complete debug output: https://www.terraform.io/docs/internals/debugging.html. Please do NOT paste the debug output in the issue; just paste a link to the Gist.

Panic Output

If Terraform produced a panic, please provide a link to a GitHub Gist containing the output of the crash.log.

Expected Behavior

What should have happened?

Actual Behavior

What actually happened?

Steps to Reproduce

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

  1. terraform apply

Important Factoids

Are there anything atypical about your accounts that we should know? For example: Running in EC2 Classic? Custom version of OpenStack? Tight ACLs?

References

Are there any other GitHub issues (open or closed) or Pull Requests that should be linked here? For example:

@aqilco
Copy link
Author

aqilco commented Apr 12, 2017

FYI, TF crashes during cleaning up an instance that was created by assumed role.

aws_instance.bender: Refreshing state... (ID: i-0bfa7721ddd4d7b79)

@jbardin
Copy link
Member

jbardin commented Apr 14, 2017

Consolidating this with #13565

@jbardin jbardin closed this as completed Apr 14, 2017
@ghost
Copy link

ghost commented Apr 14, 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 14, 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

3 participants