-
Notifications
You must be signed in to change notification settings - Fork 9.5k
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 0.7.6 crash during refresh with azurerm provider #9461
Comments
I think I may have found some of the logic that leads to this crash. (Not really enough to open a PR, but I wanted to get this written down before I forget about it.) The actual crash appears to occur starting in this block of code that handles interpreting the boot diagnostics portion of the Azure API response.
What I think is happening here is that Terraform appears to blindly assume that if diagnosticsProfile and bootDiagnostics are not nil in the raw results then Azure will have of course returned both the enabled / disabled boolean and the URI for the storage account. It appears that Azure considers it perfectly valid to only return Assuming I'm right here I have a new procedure that I think will reproduce this crash:
|
Thanks for letting me know! |
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. |
Terraform Version
0.7.6 (was last working in 0.7.3)
Affected Resource(s)
Terraform Configuration Files
Link
Debug Output
Link
Panic Output
Included with the config files.
Expected Behavior
Terraform should have been able to refresh and build a new plan.
Actual Behavior
Terraform hits a SIGSEGV during the refresh and writes out a crash log.
Steps to Reproduce
terraform refresh
using the above configImportant Factoids
Another group here is using Terraform 0.7.4 against the same Azure account, but in different resource groups and they have not encountered any issues that lead to Terraform panicking like this.
References
I suspect this is the same failure that I was seeing in issue 8995. I also noticed that issue 9410 appears to have a very similar stack trace, but inside azurerm_virtual_network instead of azurerm_virtual_machine.
The text was updated successfully, but these errors were encountered: