Multiple deleted PostgreSQL Flexible Servers stuck in 'Dropping' state

Question

A few hours ago, I deleted two resource groups that included, among other resources, PostgreSQL Flexible Servers. All other resources were successfully deleted, but the PostgreSQL servers remain.

In the Azure Portal, their overview pages display the error: "Cannot read properties of undefined (reading 'createdAt')"

Upon further inspection, both servers appear to be stuck in the Dropping state. These resources cannot be managed or removed through the portal or CLI.

How can I get rid of them?

Answer 1

Hello KS

Following up on the discussion, the Azure Database for PostgreSQL Flexible Server in the Azure portal is currently stuck in the dropping state.

As mentioned, we attempted to drop the servers from the backend.

I hope this has been helpful!

Your feedback is important so please take a moment to accept answers. If you still have questions, please let us know what is needed in the comments so the question can be answered. Thank you for helping to improve Microsoft Q&A!

If this answers your query, do click Accept Answer and Upvote for was this answer helpful.

Answer 2

Hello KS,

Welcome to the Microsoft Q&A and thank you for posting your questions here.

I understand that you are having multiple deleted PostgreSQL Flexible Servers stuck in 'Dropping' state.

From experience so far, when PostgreSQL Flexible Servers are stuck in "Dropping" state due to backend corruption, only Microsoft Internal can fix this, however, follow the steps to resolve it:

Step 1: Bypasses portal UI limitations to force deletion via Azure CLI

az resource delete --ids /subscriptions/<SUBSCRIPTION_ID>/resourceGroups/<RG_NAME>/providers/Microsoft.DBforPostgreSQL/flexibleServers/<SERVER_NAME>

You should expect that it can fails if backend state is corrupted (likely), but rules out CLI misconfiguration. Check more details in the docs - https://learn.microsoft.com/en-us/cli/azure/resource?view=azure-cli-latest#az-resource-delete

Step 2: Prevent future occurrences:

1. Delete PostgreSQL servers individually before deleting the Resource Goup.
2. Use Azure Resource Graph to confirm server state pre-deletion:

        Resources
        | where type == "microsoft.dbforpostgresql/flexibleservers"
        | project name, resourceGroup, properties.provisioningState

Check steps and read more details in https://learn.microsoft.com/en-us/azure/governance/resource-graph/ Also, avoid naming issue by waiting for 72 hours before reusing server names.

Step 3: If all fails, submit a critical support ticket and escalate via Azure Admin Channels

How to create Azure support requests is here - https://learn.microsoft.com/en-us/azure/azure-portal/supportability/how-to-create-azure-support-request and Azure Admin Center - https://admin.microsoft.com for subscription-level escalation.

I hope this is helpful! Do not hesitate to let me know if you have any other questions or clarifications.

---

Please don't forget to close up the thread here by upvoting and accept it as an answer if it is helpful.