'Azure Database for PostgreSQL single server' auto-migration to flexible server stuck

Oliver Johannsen 0 Reputation points
2024-09-17T21:57:58.96+00:00

I was forced into an auto-migration, and was told it'd be problemfree - now my service has been stuck in "in-progress" for over 24 hours. There is still no sign of a flexible server in any of my resources, but Service Health is falsely reporting that it was successful.

It has changed the server name to a new string on the resource, but still accepting connections through the old URL.

What do I do? Being forced into an auto-migration process, to then have it report multiple truths about what has happened, and no way to access or configure DB (since no DB resources match the server name of production database) - with no way of contacting support without paying 30$ is absolutely ludicrous.

Azure Database for PostgreSQL
{count} votes

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.