Crash on destroy
#869
Labels
Comments
|
Hey there - sorry you hit this! Let's see if we can get it figured out. Pulling out the important lines here: Any chance you could share the relevant bits of your terraform config and statefile? |
|
This the relevant part of my config: resource "aws_vpc" "prd_plntr" {
cidr_block = "172.31.0.0/16"
tags {
Name = "prd.plntr-vpc"
}
}
resource "aws_subnet" "a_prd_plntr" {
vpc_id = "${aws_vpc.prd_plntr.id}"
cidr_block = "172.31.0.0/19"
availability_zone = "${concat(var.aws_region, "a")}"
tags {
Name = "a.prd.plntr-subnet"
}
}
resource "aws_subnet" "c_prd_plntr" {
vpc_id = "${aws_vpc.prd_plntr.id}"
cidr_block = "172.31.64.0/19"
availability_zone = "${concat(var.aws_region, "c")}"
tags {
Name = "c.prd.plntr-subnet"
}
}
resource "aws_internet_gateway" "prd_plntr" {
vpc_id = "${aws_vpc.prd_plntr.id}"
}
... Other stuff is configured here: route tables, security groups ...Just in case: $ terraform --version
Terraform v0.3.5Tell me if you need more info. |
|
Great - let me see if I can reproduce the scenario here. |
|
Ok here are the steps I took. Made config as above. Did
Got AZ error because Modified to use Performed the modifications you stated above:
Then Manually edited
Do you see any important steps I'm missing to get something closer to your scenario? |
|
As I said, I'm not really sure about what happened. I just played with terraform: applying and then destroying my configuration. The configuration:
The steps should look similar to:
Note: step5 fails with |
|
Thanks for providing all these details! Hopefully this will give me enough to reproduce and diagnose. |
|
Luckily, I still had the terminal output. If that's not enough, than it's easier to close the issue. I've discovered the tool ( Anyway, that's a great tool! I'm sure I'll use it in future. |
|
OK. Thanks. I have Homebrew's version of terraform. I don't really want to build it from master, and then maintain it by myself. Anyway, for now I've upgraded to 0.3.6. |
|
Sounds good... closing as fixed for now - feel free to reopen if you see additional sadness you think we should look in to 👍 |
|
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
locked and limited conversation to collaborators
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I am not really sure what happened.
AWS state:
Contents of
crash.log:The text was updated successfully, but these errors were encountered: