-
Notifications
You must be signed in to change notification settings - Fork 4.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
Error: Provider produced inconsistent result after apply #10227
Comments
Facing the same issue with azurerm Version
logs
|
I had the same error with azurerm_role_definition, upgrading to the latest version of TF and provider seems to have fixed it for me.
|
👋 Taking a look through here whilst the issue is slightly different, I believe the root cause is the same issue as in #10371, so rather than having multiple issues open tracking the same thing, I'm going to close this in favour of #10371 - would you mind subscribing to that issue for updates? Thanks! |
/reopen still seeing this issue with
|
This issue still happens with
|
@tombuildsstuff could you reopen |
It seems to me that this happens when multiple terraform scripts write secrets to the same key vault that has not been created by terraform itself (or a different terraform run). Is this not supported? |
@alxy yes I see same. In my case first plan creates Key Vault is created by Terraform plan. Then a Run Trigger kicks off another plan that fails when trying to add a secret to Key Vault. I'm using |
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! |
Community Note
Terraform (and AzureRM Provider) Version
Affected Resource(s)
azurerm_key_vault_secret
Terraform Configuration Files
Debug Output
Panic Output
none
Expected Behaviour
works
Actual Behaviour
Steps to Reproduce
Running plan from Terraform Cloud workspace.
This is intermittent. Typically we just re-run and the issue goes away.
References
I'm assuming this is an azurerm provider issues based on this hashicorp/terraform#20688
The text was updated successfully, but these errors were encountered: