-
Notifications
You must be signed in to change notification settings - Fork 9.6k
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
bug?: 0.12.x -> 0.13.x: provider version in state: "Error: Could not load plugin"... #26104
Comments
update: replace-provider seemed to do the trick, is this the appropriate action for this situation?
|
Hi @tony-kerz! Sorry for this odd behavior and thanks for reporting it. The What seems odd here, and perhaps worthy of some more attention even though you've found a workaround, is that we expect In your case it seems like I don't believe we've seen this particular situation -- where |
See hashicorp/terraform-provider-tfe#209 and #26075 for additional examples. |
I ran into the same problem with a provider
|
I have the same with aws and archive providers. I can't provide full trace logs but maybe these can help Interesting also that after I used the replace-providers with successful planning, sequential planning and apply didn't found "matching provider" for the one with '-'
|
I'm seeing the same thing with the azurerm provider.
|
Thanks @tony-kerz, this workaround working for me |
|
Dropping this here in case it can help in further troubleshooting or workarounds. The
This dropped a mysterious error in the plan output:
So I reverted the change and then the next plan and apply worked without error. |
I should have expected this, but my "workaround" didn't work on another workspace with the same defect. |
OK, total face palm moment. Not only was I wrong about Hopefully some day this will all be less mysterious to me. |
I am facing similar issue while running terraform init.
Error: Failed to install provider Error while installing hashicorp/archive v2.0.0: open |
facing similar kind of issue while running terraform init command. backend "remote" {
} required_providers { provider "aws" {} Error
Error: Failed to install provider .terraform\plugins\registry.terraform.io\hashicorp\archive\2.0.0\windows_amd64\terraform-provider-archive_v2.0.0_x5.exe: |
I think I've managed to figure out what's going on here. This can only happen when using workspaces. When I cleared my |
@agaffney Thanks, this worked for me. Manually running the |
I can confirm that @agaffney's fix worked for me as well. I was having the exact same issue with the Azurerm provider. The double init did the trick. Thanks! |
On
when I try to
Very frustrated... |
@Hoiy don't think your issue is related. TF v0.13.x requires the providers be listed in this new format and should auto-generate a |
Perfect FIX for the issue. thanks !! |
Hello All, The issue originally submitted here has been worked around, and we have not seen able to reproduce the upgrade in newer releases. Most of the other issues here are unrelated, and can be caused by a variety of other misconfigurations. New questions should be directed to the community forum where there are more people ready to help. If you have a reproduction of a similar error with the most recent release of terraform, please file a new issue with all the relevant information. 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 Version
Terraform Configuration Files
Expected Behavior
terraform allows provider versions referenced in state to be modified by newer providers in newer versions of code
Actual Behavior
Additional Context
The text was updated successfully, but these errors were encountered: