Loading...
Loading...
### Terraform Version ``` $ terraform version Terraform v0.13.4 ``` ### Terraform Configuration Files https://github.com/Tensho/terraform-issue-plugin-cache-assasination ### Debug Output ``` $ TF_LOG=trace ./script.sh ... 2020/10/02 14:52:45 [TRACE] providercache.fillMetaCache: error while scanning directory .terraform/plugins: failed to read metadata about .terraform/plugins/registry.terraform.io/hashicorp/null/2.1.0/darwin_amd64: stat .terraform/plugins/registry.terraform.io/hashicorp/null/2.1.0/darwin_amd64: no such file or directory Error: Failed to validate installed provider Validating provider hashicorp/archive v1.3.0 failed: selected package for registry.terraform.io/hashicorp/archive is no longer present in the target directory; this is a bug in Terraform ``` ### Expected Behavior Terraform should initialize (providers) in the project directory without any errors. ### Actual Behavior Terraform raises `Failed to validate installed provider` error. ### Steps to Reproduce WARNING: This script may delete your provider cache directory if it's placed in `~/.terraform.d/providers-cache`. ``` $ TF_LOG=trace ./script.sh ``` ### Additional Context The root of the problem is symlink from `.terraform/plugins` directory to providers cache directory: ``` .terraform/plugins/registry.terraform.io/hashicorp/null/2.1.0/darwin_amd64 –> ~/.terraform.d/provider-cache/registry.terraform.io/hashicorp/null/2.1.0/darwin_amd64 ``` I think Terraform should skip or better remove the broken symlinks to disappeared provider binaries.
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.