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 plan coredumps on new and old code #1941

Closed
georgespatton opened this issue Sep 18, 2018 · 5 comments · Fixed by #1947
Closed

Terraform plan coredumps on new and old code #1941

georgespatton opened this issue Sep 18, 2018 · 5 comments · Fixed by #1947

Comments

@georgespatton
Copy link

georgespatton commented Sep 18, 2018

Using the latest version:

Terraform v0.11.8

  • provider.azurerm v1.15.0
  • provider.random v2.0.0

Terraform is crashing. I tried going back to old code as well as old versions of the provider.azurerm and provider.random providers. See this gist.

https://gist.github.com/georgespatton/34780ec9352998d371f8a4d99b6969fe

Steps to Reproduce

  1. terraform plan

This worked 24 hours ago.

@abrocklesby
Copy link

Also experiencing this unexpected EOF error during plan with azurerm v1.15.0 works ok with with v1.13.0 & v1.14.0

@georgespatton
Copy link
Author

georgespatton commented Sep 19, 2018

Downgrading to v1.13.0 with terraform v0.11.8 also crashes. Also tried v1.13.0 with terraform v0.11.7 and didn't work. Then, I went into Azure, removed two instances that were in terraform config that had failed initialization. Then ran terraform plan again and it worked. I tried on all the above versions and they all worked. It appears that the problem is when an Azure virtual machine is in a failed state that it causes terraform to crash during a terraform plan.

To replicate, create a virtual machine in terraform for Azure. Have the machine get into a failed initialation state (for example, delete the virtual machine after initial creation but leave the disk), then try to do a terrraform plan against Azure. It should get back into this state.

@georgespatton
Copy link
Author

Looks great, we'll anticipate this in the 1.16.0 release. Thanks for the quick turnaround. Amazing work here.

@tombuildsstuff
Copy link
Contributor

hey @georgespatton @abrocklesby

Just to let you know that this fix has now landed in v1.16 of the AzureRM Provider (here's the full changelog](https://github.com/terraform-providers/terraform-provider-azurerm/blob/v1.16.0/CHANGELOG.md)). You can upgrade to to this version by specifying it in your provider block:

provider "azurerm" {
  version = "=1.16.0"
}

... and then running terraform init -upgrade :)

Thanks!

@ghost
Copy link

ghost commented Mar 6, 2019

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 feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 [email protected]. Thanks!

@ghost ghost locked and limited conversation to collaborators Mar 6, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants