You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am experiencing a crash when using Terraform v0.9.2+
The crash.log shows that a response from the Azure API returns a azurerm_virtual_machine configuration with a network Interface and an empty properties field.
On Line 659 it is checked if NetworkInterfaceReferenceProperties is nil, which is not when a empty properties field is returned. The following attempt to access the "Primary" key is resulting in a nil pointer dereference.
I'm not sure if it is a Bug at Azure site that an empty properties field is returned. If not, it must be further checked if the properties field is empty before trying to access a key.
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 👉 hashibot-feedback@hashicorp.com. Thanks!
ghost
locked and limited conversation to collaborators
Apr 1, 2020
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hi there,
I am experiencing a crash when using Terraform v0.9.2+
The crash.log shows that a response from the Azure API returns a azurerm_virtual_machine configuration with a network Interface and an empty properties field.
The Bug was introduced with Commit
On Line 659 it is checked if NetworkInterfaceReferenceProperties is nil, which is not when a empty properties field is returned. The following attempt to access the "Primary" key is resulting in a nil pointer dereference.
I'm not sure if it is a Bug at Azure site that an empty properties field is returned. If not, it must be further checked if the properties field is empty before trying to access a key.
Affected Resource(s)
Panic Output
crash.log
The text was updated successfully, but these errors were encountered: