Azure PostgreSQL Flexible Server Creation Fails with InternalServerError

Question

Azure PostgreSQL Flexible Server Creation Fails with InternalServerError

karim sellami 5

Hi,

I'm not able to provision an Azure PostgreSQL Flexible Server. I got the following error:

polling after Create: polling failed: the Azure API returned the following error:

│

│ Status: "InternalServerError"

│ Code: ""

│ Message: "An unexpected error occured while processing the request. Tracking ID: 'b0df1034-8152-4017-9782-42d43c8b0962'"

│ Activity Id: ""

│

│ ---

│

│ API Response:

│

│ ----[start]----

│ {"name":"819bc68a-4f86-4e3f-89e7-f5ada93264c6","status":"Failed","startTime":"2024-08-27T13:59:28.823Z","error":{"code":"InternalServerError","message":"An unexpected error occured while processing the request. Tracking ID: 'b0df1034-8152-4017-9782-42d43c8b0962'"}}

│ -----[end]-----

Could you help troubleshoot the issue?

Sai Raghunadh M 4,570 Reputation points Microsoft External Staff Moderator

2024-09-24T15:05:14.2933333+00:00

Hi @karim sellami,

Thanks for the question and using MS Q&A platform

The error seems to be a transient error that resolves on its own sometimes.

For more information, please go through this documentation: Transient errors.

If the issue continues, reaching out to Azure Support with the tracking ID can help you get more information.

I hope this information helps, please do let us know if you have any Queries.
Sai Raghunadh M 4,570 Reputation points Microsoft External Staff Moderator

2024-09-25T15:19:44.22+00:00

Hi @karim sellami,

We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help.
Sai Raghunadh M 4,570 Reputation points Microsoft External Staff Moderator

2024-09-27T08:13:13.3+00:00

Hi @karim sellami,

We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help.

2 answers

Your answer

Sai Raghunadh M 4,570 Reputation points Microsoft External Staff Moderator

2024-09-24T15:05:14.2933333+00:00

Hi @karim sellami,

Thanks for the question and using MS Q&A platform

The error seems to be a transient error that resolves on its own sometimes.

For more information, please go through this documentation: Transient errors.

If the issue continues, reaching out to Azure Support with the tracking ID can help you get more information.

I hope this information helps, please do let us know if you have any Queries.
Sai Raghunadh M 4,570 Reputation points Microsoft External Staff Moderator

2024-09-25T15:19:44.22+00:00

Hi @karim sellami,

We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help.
Sai Raghunadh M 4,570 Reputation points Microsoft External Staff Moderator

2024-09-27T08:13:13.3+00:00

Hi @karim sellami,

We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help.

Answer 1

RahulRandive 10,501 Volunteer Moderator

Hi @karim sellami

We have experienced in the past that deployments often fail due to capacity issues in specific regions. If the region isn't constrained, consider creating the server in another region.

Also, have you also tried creating the server through the portal?

Let us know if you have any question.

Thank You

karim sellami 5 Reputation points

2024-08-28T10:41:20.8533333+00:00

Hi @RahulRandive, I was able to create the server via the portal using the same region and sku. Any other suggestion ?

Answer 2

I was getting this same error and I ended up putting in an Azure Support request. In summary this was their response:

"Our feedback: We would like to confirm that there is a current Azure capacity constraint in “East US” region and availability of SKU and capacity to provision a new instance may not complete unfortunately. We apologize for this current capacity constraint."

I was able to create a PostgreSQL Flexible Server in East US 2. Clearly the error message needs to be more clear as they were also able to see this error in their end:
"Virtual machine creation failed. code: ProvisioningState/failed/ZonalAllocationFailed, level: Error, displayStatus: Provisioning failed, message: Allocation failed. We do not have sufficient capacity for the requested VM size in this zone. Read more about improving likelihood of allocation success at http://aka.ms/allocation-guidance "

Share via

Azure PostgreSQL Flexible Server Creation Fails with InternalServerError

2 answers

Your answer