azurerm_role_assignment produced an unexpected new value: Root resource was present, but now absent

[patpicos]

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

Terraform (and AzureRM Provider) Version

Terraform v0.15.5
on linux_amd64
+ provider registry.terraform.io/hashicorp/azurerm v2.62.0
+ provider registry.terraform.io/hashicorp/random v3.1.0
+ provider registry.terraform.io/hashicorp/template v2.2.0

Affected Resource(s)

+ provider registry.terraform.io/hashicorp/azurerm v2.62.0
+ provider registry.terraform.io/hashicorp/random v3.1.0
+ provider registry.terraform.io/hashicorp/template v2.2.0

Terraform Configuration Files

# Affected resource only:
resource "azurerm_role_assignment" "assign" {
  for_each     = var.assign_mi_to_scopes != null ? var.assign_mi_to_scopes : {}
  principal_id = azurerm_user_assigned_identity.this.principal_id

  scope                = lookup(each.value, "scope", null)
  role_definition_name = lookup(each.value, "role_definition_name", null)
}

Debug Output

Panic Output

Expected Behaviour

The role assignment added

Actual Behaviour

Failure with inconsistent result

Error: Provider produced inconsistent result after apply

When applying changes to
module.oracle1.azurerm_role_assignment.assign["platform_sa"], provider
"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.

Steps to Reproduce

1. terraform apply

Important Factoids

None

References

• Error in azurerm_role_assignment #12060

[patpicos]

closing as duplicate. Confirmed downgrading to azurerm 2.61 provides a workaround

[github-actions]

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.