Creating subnet/route table association fails with 'Provider produced inconsistent result after apply' error

[topolodgy]

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 v1.0.4

• provider registry.terraform.io/hashicorp/azurerm v2.71.0

Affected Resource(s)

azurerm_subnet_route_table_association

• azurerm_XXXXX

Terraform Configuration Files

resource "azurerm_subnet_route_table_association" "private_routetable_association" {
  for_each       = var.prvsubnet_id
  subnet_id      = each.value
  route_table_id = azurerm_route_table.private_route_table[0].id
}

Debug Output

Panic Output

Expected Behaviour

Existing route table should have been associated with all existing private subnets listed as a map in var.prvsubnet_id.

Actual Behaviour

4 of 5 subnets in the map were successfully associated with the route table, the 5th failed. Error provided states:

│ Error: Provider produced inconsistent result after apply
│
│ When applying changes to module.routes.azurerm_subnet_route_table_association.naas_private_routetable_association["inf"], 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

References

I assume this is provider-related, based on the error presented and this issue:

hashicorp/terraform#20688

This issue also appears related:

#10227

• #0000