Production PostgreSQL Flexible Server is stuck in the validatingmajorversionupgrade state after initiating the PostgreSQL 16 pre-validation. Please investigate and assist in restoring the server to a healthy state.

Question

The production Azure Database for PostgreSQL Flexible Server (biolabs-production-primary-server) has been stuck in the validatingmajorversionupgrade state for over 48 hours following a failed PostgreSQL 16 pre-validation. The issue began during the Azure Service Health incident (Tracking ID: TQB2-64G) affecting East US. The production application is healthy and database connectivity is unaffected, but all management operations remain blocked. We request assistance in clearing the stuck operation and restoring the server to a healthy management state.

Answer 1

Hi @Generic New Vision/BioLabs Admin

Thank you for your patience while we investigated this issue.

We have completed our review and can confirm that the server is now in a Succeeded state and is no longer stuck in the validatingmajorversionupgrade status.

Could you please retry the operation from your side and let us know the outcome? If you encounter any further issues or errors, please share the details and we will continue to assist.

Answer 2

hi Generic New Vision/BioLabs Admin & thx for sharing urs issue here at Q&A portal,

stuck control-plane operation rather than a database engine issue.

If the server has remained in validatingmajorversionupgrade for more than 48 hours, management operations are blocked, and the application continues to connect normally, it suggests the pre-validation workflow never completed or failed to clean up after the East US service incident. There isn't a customer-facing action to clear that state.

Given the timing with Service Health incident TQB2-64G, it's worth mentioning that correlation in your support request, as the failed validation may have been impacted by the regional incident.

At this point, the PostgreSQL Flexible Server engineering team will need to inspect the backend operation, clear the stale validation state, or complete/roll back the pre-validation workflow. Include the server name, subscription ID, region, approximate UTC timestamp when the validation started, and reference the Service Health tracking ID.

Retrying the major version validation or attempting additional management operations is unlikely to help while the server remains in the validatingmajorversionupgrade state. This requires backend intervention to restore the server to a healthy management state.

rgds,

Alex

&

If my answer was helpful pls mark it and additional thx if u follow me at Q&A portal

and at my blog https://ctrlaltdel.blog/