-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
Trying to connect to Azure through terraform #15487
Comments
I enabled trace logging and noticed that we're getting these errors. A quick google showed several recent go issues when using WSL so I tried in a Linux VM and it worked. |
👋 As @seumasdunlop has mentioned above, we've had a few reports of users encountering this issue when using WSL - from our research it appears to be an issue where the IPv4 addresses aren't correctly resolved by the default DNS server when running in WSL. Other users have been able to workaround this by updating their DNS Servers (to CloudFlare/Google/OpenDNS etc) within WSL which has fixed this for them - however since this appears to be a WSL issue rather than something specific to Terraform, I'm going to close this issue for the moment but I'd recommend opening an issue on the WSL repository where someone from Microsoft should be able to take a look. Thanks! |
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. |
Terraform (and AzureRM Provider) Version
Terraform v1.1.6
on linux_amd64
Affected Resource(s)
All
Terraform Configuration Files
PROVIDERS
Expected Behaviour
Terraform to refresh state
Actual Behaviour
Steps to Reproduce
terraform apply
or 'terraform plan' and it will get stuckImportant Factoids
Never had this issue before
The text was updated successfully, but these errors were encountered: