This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(182.40000000000003, 18%, 27%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ETR%3C/text%3E%3C/svg%3E)
Received an error when originally deploying a postgreSQL flexible server in East US via Terraform:
InternalServerError An unexpected error occured while processing the request
Now it is stuck in "Provisioning" and if I click into the resource it shows:
Cannot read properties of undefined (reading 'createdAt')
Tried deleting it via the CLI, but it says it can't find any such resource:
az postgres flexible-server delete --resource-group <rg-name> --name <db-name>
Also tried clicking into the resource group and deleting the resource there which also failed.
I also tried re-deploying it via Terraform and also via the Azure UI and both failed with the same InternalServerError.
We need to keep the name of this server, so we can't retry deploying under a different name.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(268.8, 8%, 36%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EST%3C/text%3E%3C/svg%3E)
Hi Tim Reed
Thank you for the details. We’re aware that some customers are experiencing PostgreSQL Flexible Servers getting stuck in “Provisioning” after an InternalServerError in East US.
Our internal team is currently investigating this issue. In the meantime:
We apologize for the inconvenience and appreciate your patience.
@Smaran Thoomu is this a known issue in the region? Or with the postgres service? We tried deploying another DB with a different name and it also failed. Can you provide some guidance on what the issue is here and how we can move forward?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(291.2, 27%, 38%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EFT%3C/text%3E%3C/svg%3E)
We also got this issue a few days ago.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(176, 62%, 27%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EPC%3C/text%3E%3C/svg%3E)
We have the same issue.
The stuck postgres servers finally removed from the UI on their own. I went ahead and updated Terraform and the azurerm TF provider to the latest versions and tried again and it worked.
Not sure if it was an outdated provider version, or if there was something else going on, but either way we got past this issue.
Did the removal take two weeks?