Loading...
Loading...
### Terraform Version ```shell Terraform v1.6.5 on darwin_amd64 ``` ### Terraform Configuration Files (none) ### Debug Output (Couldn't reproduce the broken DNS state, so was too late to get debug output.) ### Expected Behavior Terraform should indicate that the DNS could not be resolved. ### Actual Behavior It gives a cryptic error message: ``` $ terraform init Initializing the backend... Initializing provider plugins... - Finding latest version of hashicorp/aws... ╷ │ Error: Failed to query available provider packages │ │ Could not retrieve the list of available versions for provider hashicorp/aws: could not connect to registry.terraform.io: │ failed to request discovery document: Get "https://registry.terraform.io/.well-known/terraform.json": context deadline │ exceeded (Client.Timeout exceeded while awaiting headers) ``` ### Steps to Reproduce 0. (Have broken DNS on Mac OS) 1. `terraform init` ### Additional Context The error went away when fixing with this answer: [DNS Name lookup (was SSH) Not Working After Snow Leopard Upgrade](https://serverfault.com/questions/64837/dns-name-lookup-was-ssh-not-working-after-snow-leopard-upgrade/65771#65771) ### References - 26532
Click on a version to see all relevant bugs
Terraform Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.