Skip to content
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

azurerm_role_assignment Error: Provider produced inconsistent result after apply #12108

Closed
isaacdan opened this issue Jun 8, 2021 · 3 comments

Comments

@isaacdan
Copy link

isaacdan commented Jun 8, 2021

Team,
My transformer pipeline is failing while creating role assignment to a managed identity which was working fine till azurerm provider 2.61

After upgrading to azurerm provider 2.62 I'm facing this issue.
Let me know if any additional info needed (screenshot attached
terraformbug
)

resource "azurerm_role_assignment" "appgw_role" {
depends_on = [azurerm_user_assigned_identity.appgw_identity]
scope = azurerm_user_assigned_identity.appgw_identity[0].id
role_definition_name = "Managed Identity Operator"
principal_id = data.azuread_service_principal.aks_obj_identity.object_id
}

Error message

Error: Provider produced inconsistent result after apply

│ When applying changes to
│ module.apcfg_kv_db.azurerm_role_assignment.appgw_role[0], provider
│ "module.apcfg_kv_db.provider["registry.terraform.io/hashicorp/azurerm"]"
│ produced an unexpected new value: Root resource was present, but now
│ absent.

│ This is a bug in the provider, which should be reported in the provider's
│ own issue tracker.

@aristosvo
Copy link
Collaborator

Hi @isaacdan!

I believe this is a duplicate of #12057, at least six issues covering this issue are opened the last few days. The PR fixing this problem is under review.

Most information how to solve it can be found under #12060

@magodo
Copy link
Collaborator

magodo commented Jun 9, 2021

I'm gonna close this issue as it is fixed by #12076, which is delivered in v2.62.1. Please feel free to reopen if the issue remains.

@magodo magodo closed this as completed Jun 9, 2021
@github-actions
Copy link

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 have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jul 10, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants