Terraform crashes attempting to destroy an azurerm_postgres_database resource

[tareks]

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.2
on linux_amd64
+ provider registry.terraform.io/hashicorp/azurerm v2.67.0

Affected Resource(s)

• azurerm_postgresql_database

Terraform Configuration Files

resource "azurerm_postgresql_database" "app" {
  name                = "test"
  resource_group_name = "my-test-rg"
  server_name         = "testpsqlserver"
  charset             = "UTF8"
  collation           = "English_United States.1252"

Debug Output

https://gist.github.com/tareks/9fb6aca59333a88ad091750a3747be63

Panic Output

https://gist.github.com/tareks/9fb6aca59333a88ad091750a3747be63

Expected Behaviour

PostgreSQL Database should have been dropped and resource destroyed.

Actual Behaviour

Terraform crashed and it appears that the database is not completed dropped.

Have to manually run a drop database command and then re-run terraform destroy for it to continue.

Steps to Reproduce

1. terraform apply
2. terraform destroy

Important Factoids

This doesn't seem to appear to happen all the time - especially on newly provisioned databases. It appears to only occur when a database has been up for a longer period of time.

References

[github-actions]

This functionality has been released in v2.71.0 of the Terraform Provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading.

For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you!

[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.