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 after upgrading to v0.13.1 in mac machine #26046

Closed
SamaChandra opened this issue Aug 28, 2020 · 4 comments
Closed

Terraform Crash after upgrading to v0.13.1 in mac machine #26046

SamaChandra opened this issue Aug 28, 2020 · 4 comments
Labels
bug new new issue not yet triaged

Comments

@SamaChandra
Copy link

Terraform Version

v0.13.1
...


### Terraform Configuration Files
<!--


-->

```terraform
...

panic: not a collection type

goroutine 10909 [running]:
github.com/zclconf/go-cty/cty.Type.ElementType(0x38e45e0, 0xc0041324d0, 0xc000e36478, 0x8)
github.com/zclconf/[email protected]/cty/collection.go:25 +0xba
github.com/hashicorp/terraform/terraform.createEmptyBlocks(0xc0022114d0, 0x38e45e0, 0xc0041324e0, 0x2efeb80, 0xc009e80d50, 0x38e45e0, 0xc0041325b8, 0x2efeb80, 0xc009e8ce40)
github.com/hashicorp/terraform/terraform/eval_read_data_plan.go:242 +0x202
github.com/hashicorp/terraform/terraform.dataObjectHasChanges(0xc0022114d0, 0x38e45e0, 0xc0041324e0, 0x2efeb80, 0xc009e80d50, 0x38e45e0, 0xc0041325b8, 0x2efeb80, 0xc009e8ce40, 0x0, ...)
github.com/hashicorp/terraform/terraform/eval_read_data_plan.go:211 +0x19e
github.com/hashicorp/terraform/terraform.(*evalReadDataPlan).Eval(0xc00a40e1e0, 0x3926080, 0xc001540270, 0x1, 0x1, 0x0, 0x0)
github.com/hashicorp/terraform/terraform/eval_read_data_plan.go:107 +0x1238
github.com/hashicorp/terraform/terraform.EvalRaw(0x387c8c0, 0xc00a40e1e0, 0x3926080, 0xc001540270, 0x0, 0x0, 0x0, 0x0)
github.com/hashicorp/terraform/terraform/eval.go:49 +0xc7
github.com/hashicorp/terraform/terraform.(*EvalSequence).Eval(0xc001a61d40, 0x3926080, 0xc001540270, 0x1, 0x1, 0x6, 0xc000baa590)
github.com/hashicorp/terraform/terraform/eval_sequence.go:20 +0xfd
github.com/hashicorp/terraform/terraform.EvalRaw(0x387c320, 0xc001a61d40, 0x3926080, 0xc001540270, 0x2eb3460, 0x4b98942, 0x2e12f00, 0xc0078af5f0)
github.com/hashicorp/terraform/terraform/eval.go:49 +0xc7
github.com/hashicorp/terraform/terraform.Eval(0x387c320, 0xc001a61d40, 0x3926080, 0xc001540270, 0xc001a61d40, 0x387c320, 0xc001a61d40, 0x0)
github.com/hashicorp/terraform/terraform/eval.go:35 +0x4d
github.com/hashicorp/terraform/terraform.(*Graph).walk.func1(0x32443e0, 0xc0078aeed0, 0x0, 0x0, 0x0)
github.com/hashicorp/terraform/terraform/graph.go:73 +0xc77
github.com/hashicorp/terraform/dag.(*Walker).walkVertex(0xc000baa480, 0x32443e0, 0xc0078aeed0, 0xc002000840)
github.com/hashicorp/terraform/dag/walk.go:387 +0x357
created by github.com/hashicorp/terraform/dag.(*Walker).Update
github.com/hashicorp/terraform/dag/walk.go:309 +0x11d7

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

SECURITY WARNING: the "crash.log" file that was created may contain
sensitive information that must be redacted before it is safe to share
on the issue tracker.

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

Debug Output

Crash Output

Expected Behavior

Actual Behavior

Steps to Reproduce

Additional Context

References

@SamaChandra SamaChandra added bug new new issue not yet triaged labels Aug 28, 2020
@nexxai
Copy link
Contributor

nexxai commented Aug 31, 2020

This bug has already been fixed here and will be included in v13.2

@andrei-dascalu
Copy link

I don't mean to be rude, but I wonder if there's a TTL for 0.13.2? The impact of the issue is quite painful.

@jbardin
Copy link
Member

jbardin commented Aug 31, 2020

Closing as duplicate of #26011

@jbardin jbardin closed this as completed Aug 31, 2020
@ghost
Copy link

ghost commented Oct 13, 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 as resolved and limited conversation to collaborators Oct 13, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug new new issue not yet triaged
Projects
None yet
Development

No branches or pull requests

4 participants