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 during plan #4019

Closed
eugenetaranov opened this issue Nov 23, 2015 · 10 comments
Closed

terraform crash during plan #4019

eugenetaranov opened this issue Nov 23, 2015 · 10 comments

Comments

@eugenetaranov
Copy link

Hello,

just tried to tun terraform pull and it crashed. Crash log attached.
Could you please look ?

crash.txt
v0.6.6, OSX

Thanks,
Eugene

@eugenetaranov
Copy link
Author

quick update, might be important: it timed out when I was running it last time during aurora cluster spinup. Maybe this broke tfstate files.

@radeksimko
Copy link
Member

Cutting out the interesting part of the crash log:

2015/11/23 12:11:44 [DEBUG] terraform-provider-aws: panic: runtime error: invalid memory address or nil pointer dereference
2015/11/23 12:11:44 [DEBUG] terraform-provider-aws: [signal 0xb code=0x1 addr=0x38 pc=0x122521]
2015/11/23 12:11:44 [DEBUG] terraform-provider-aws: 
2015/11/23 12:11:44 [DEBUG] terraform-provider-aws: goroutine 65 [running]:
2015/11/23 12:11:44 [DEBUG] terraform-provider-aws: github.com/hashicorp/terraform/builtin/providers/aws.resourceAwsRDSClusterInstanceRead(0xc2083e3e00, 0x7c65c0, 0xc2080be840, 0x0, 0x0)
2015/11/23 12:11:44 [DEBUG] terraform-provider-aws:     /opt/gopath/src/github.com/hashicorp/terraform/builtin/providers/aws/resource_aws_rds_cluster_instance.go:135 +0x321

@jen20
Copy link
Contributor

jen20 commented Nov 23, 2015

Hi @eugenetaranov! Thanks for reporting this crash. Could you confirm the command you were executing when you saw this crash? From looking at the code paths and discussing with @phinze, it doesn't seem like a simple terraform remote pull could cause execution to follow this path as it doesn't refresh. If you could confirm what you were doing it will make investigation a lot easier!

@eugenetaranov
Copy link
Author

Hi,
you are correct, I think I made a typo, sorry for that. Command was "~/bin/terraform/terraform plan"

@catsby
Copy link
Contributor

catsby commented Nov 23, 2015

Hey @eugenetaranov – was the Cluster Instance renamed, or are there multiple instances with a similar name by any chance?

@catsby catsby added the waiting-response An issue/pull request is waiting for a response from the community label Nov 23, 2015
@eugenetaranov
Copy link
Author

Nope, it was not renamed afaik, but there was aws_rds_cluster_instance resource with count set to 2:

resource "aws_rds_cluster_instance" "cluster_instances" {
count = 1
identifier = "${var.appname}-${var.env}"
cluster_identifier = "${var.appname}-${var.env}"
instance_class = "${var.rds_instance_class}"
publicly_accessible = false
db_subnet_group_name = "${var.appname}-${var.env}-default"
}

@catsby
Copy link
Contributor

catsby commented Nov 23, 2015

If you have the configuration that would be helpful, omitting any secrets. I'll continue to dig in as well, thanks!

@catsby catsby removed the waiting-response An issue/pull request is waiting for a response from the community label Nov 23, 2015
@eugenetaranov
Copy link
Author

edited last reply, please see if it is enough

@phinze phinze changed the title terraform crash during pull terraform crash during plan Nov 24, 2015
@phinze
Copy link
Contributor

phinze commented Mar 18, 2016

Hi @eugenetaranov - this crash should be fixed with #5717 which landed today and will be included in the 0.6.14 release slated for Monday. 👍

@phinze phinze closed this as completed Mar 18, 2016
@ghost
Copy link

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

5 participants