Postgres Flexible Server stuck on updating state

Question

I have several Postgres Flexible server in my subscription that are stuck in updating state.

I try to follow this guid (https://learn.microsoft.com/en-us/answers/questions/2149493/azure-database-for-postgresql-flexible-server-stuc) but without success.

Can you help me?

Regards

Answer 1

Hi Lorenzo Carlà,

The servers were stuck in the Updating state due to subnet IP exhaustion. During maintenance or upgrade operations, PostgreSQL Flexible Server requires additional IPs, and the delegated subnet did not have sufficient usable IP addresses. This impacted 9 servers and blocked the workflow.

We have unstuck the workflow from the backend, and the servers have recovered. To prevent this from happening again especially during future upgrades. we strongly recommend increasing the subnet size, particularly for HA enabled servers. The issue may reoccur if the subnet remains constrained.

Please let us know if you have any questions and concerns.

Answer 2

If your Azure Database for PostgreSQL Flexible Servers are stuck in the updating state, it may be due to several reasons, including capacity issues or ongoing maintenance tasks. Here are some steps you can take to troubleshoot the situation:

1. Check Server State: Ensure that the servers are indeed in the updating state and not in another state that might prevent updates.
2. Capacity Issues: Sometimes, starting a server depends on the available capacity in the region. If there are capacity outages, the server start operation may not succeed. You may want to check the Azure status page or your subscription limits.
3. Wait for Completion: If the server is undergoing updates, it may take some time to complete. Azure typically handles updates automatically, but it can take longer during peak times.
4. Manual Restart: If the server remains stuck for an extended period, you might consider restarting the server. However, ensure that the server is in a state that allows for a restart.
5. Contact Support: If the issue persists, it may be necessary to contact Azure support for assistance, as they can provide more detailed insights into the server's status and any underlying issues.

Make sure to monitor the Azure portal for any notifications or alerts related to your servers, as these can provide additional context on the situation.