Select Language:
If your PostgreSQL Flexible Server has been stuck in the “Dropping” state for more than two days, it can be frustrating. Luckily, there are some steps you can take to resolve this situation, especially if standard methods haven’t worked.
First, it’s common for this issue to stem from what’s called a control-plane inconsistency. This means the cloud platform’s management system (the resource provider or RP) still shows the server as “dropping,” but behind the scenes, the server has already been removed, causing conflicts.
Start by confirming that the resource is no longer visible in the Azure portal or via CLI commands. Even if it appears to be stuck, the resource might have been deleted at the backend but still shows up in the portal or management API due to sync issues.
If the usual delete commands or portal options didn’t work—meaning attempts to delete, start, or stop the server produce errors like “404 Not Found”—your next step is to review specific logs or correlation IDs linked to the failed delete operation. While this kind of issue often requires backend support, you can prepare all relevant details, including these IDs.
Since you’re on a developer subscription and can’t open a paid support ticket, you should reach out to Azure support through the Azure forums or community channels. Provide them with the correlation IDs, resource details, and a detailed description of the steps you’ve already tried. These details are crucial for support teams to investigate and manually intervene if needed.
In the meantime, consider these additional troubleshooting steps:
– Check if there are any locks on the resource that might prevent deletion.
– Ensure no other operations are pending on your resource group.
– Review Azure Activity Log for any failed delete or update operations related to the server.
While waiting for backend intervention, avoid trying to recreate or manually modify the resource, as that might complicate recovery. Usually, support teams can clear the stuck operation from their end, either by force-purging it or resetting the resource’s state.
In summary, the key steps are:
1. Confirm the resource’s status and logs.
2. Gather relevant operation IDs and details.
3. Reach out to Azure support via community or support channels, providing all your information.
4. Wait for backend assistance to clear the stuck state.
Handling these kinds of issues might be slow, but with the right support, your server should eventually be fully released and available for further use.
ChatGPT
Perplexity
Gemini AI
Grok AI
