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
From what I can see, this issue has been fixed in #6 (which has been merged). Until that's released, you can workaround the deadlock issue you're seeing by renaming either the Virtual Network or the Subnet's name (for example by suffixing vn and sn) - or by compiling a pre-release version of the AzureRM Provider from master if you're comfortable with that.
Seeing as this issue appears to be fixed - I'm going to close this issue out for the moment. Would you be able to confirm if one of the above solutions solves your issue in the interim?
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.
Terraform Version
Terraform v0.9.8
Affected Resource(s)
Terraform Configuration Files
Debug Output
https://gist.github.com/anonymous/c3f29db46cac1487619e8d9c9fe515c6
Expected Behavior
It should've created the resource group, network + subnet.
Actual Behavior
It got stuck at creating the subnet forever. I waited for upto 30 minutes before giving up. Tried multiple times, same behavior.
Steps to Reproduce
terraform apply
The text was updated successfully, but these errors were encountered: