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 suspect this is a regression caused by one of the below PRs, as configs like this used to work for us, and reverting the locks that were added in those fixes the problem:
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.
This issue was originally opened by @cberner as hashicorp/terraform#15204. It was migrated here as part of the provider split. The original body of the issue is below.
Terraform Version
0.9.6
Affected Resource(s)
azurerm_subnet
Terraform Configuration Files
https://github.com/cberner/terraform-hang
Expected Behavior
All resources should be created
Actual Behavior
Terraform hangs (I waited over 10min) creating
module.etcd_junk.azurerm_subnet.etcd
Steps to Reproduce
Please list the steps required to reproduce the issue, for example:
git clone https://github.com/cberner/terraform-hang
cd terraform-hang/main
terraform apply
References
I suspect this is a regression caused by one of the below PRs, as configs like this used to work for us, and reverting the locks that were added in those fixes the problem:
The text was updated successfully, but these errors were encountered: