Error when upgrading Postgres Flexible server from 11 to 16

Question

When upgrading postgres flexible server 11 to 16, we are getting below error.

      "trackingId": "bb32953d-8ec2-458c-80ff-6a19a766ad38",
      "statusCode": "Conflict",
      "statusMessage": {
        "status": "Failed",
        "error": {
          "code": "InternalServerError",
          "message": "An unexpected error occured while processing the request. Tracking ID: '370cdd5f-5ef2-4e7a-9aed-7fdf088bc6db'"
        }
      },

Answer 1

Hi 4um,
It looks like you're running into an issue while trying to upgrade your PostgreSQL Flexible Server from version 11 to 16. The error message indicates a "Conflict" with the status code of "InternalServerError." Here are a few steps you can take to troubleshoot this problem:

1. Pre-Upgrade Checks: Make sure there are no long-running transactions or high workloads on the server during the upgrade, as these can cause the upgrade process to fail.

Review the Logs: Before attempting the upgrade again, enable server logs. Check the logs for any specific messages related to your attempted upgrade. These logs may provide more detail about the error you're encountering.

Compatibility Issues: Verify that none of the extensions you are using in your PostgreSQL server are unsupported for version 16. In-place upgrades currently do not support extensions like Timescaledb and pgaudit, so it's essential to make sure you're not using any of those.

Capacity Issues: If you're operating in the East US region, be aware that there may be capacity constraints affecting your ability to upgrade. You can check Azure's documentation on resolving capacity errors for more insights.

Network Access: Ensure that network traffic to PostgreSQL ports (5432 and 6432) is allowed within your virtual network, as blocking this could also contribute to upgrade issues.

If these steps don’t resolve the issue, consider creating a support case with Azure support for further assistance.

Before I conclude, I have a few follow-up questions that would help in diagnosing the issue further:

• Are you currently running any long-running transactions or high workloads on the database during the upgrade attempt?
• Have you checked if there are any unsupported extensions in your current setup?
• Can you confirm whether you're experiencing this upgrade issue in a specific region, like East US?
• Are the necessary ports open for network traffic as per your configuration?

Hope this helps! If you need more assistance, feel free to ask!
References:

• Upgrade Azure Database for PostgreSQL: Key Steps and Considerations
• Major Version Upgrade Logs
• Resolve capacity errors for Azure Database for PostgreSQL

Answer 2

The error you are encountering when upgrading your PostgreSQL flexible server from version 11 to 16 appears to be an internal server error, as indicated by the status code "Conflict" and the message stating that "An unexpected error occurred while processing the request." This type of error can occur due to various reasons, such as resource constraints, configuration issues, or service limitations within Azure.

To troubleshoot this issue, consider the following steps:

1. Check Resource Availability: Ensure that your Azure subscription has sufficient resources available for the upgrade process.
2. Review Logs: Look into the Azure activity logs for more detailed error messages that might provide insight into what went wrong during the upgrade.
3. Retry the Upgrade: Sometimes, transient errors can occur. Attempting the upgrade again after some time might resolve the issue.
4. Contact Azure Support: If the problem persists, consider reaching out to Azure support with the tracking ID provided in the error message for further assistance.

These steps should help you identify and potentially resolve the issue you're facing during the upgrade process.