Postgres covert to HA failed
injung
PROOP

2 months ago

Hi, I’m trying to convert my Postgres instance to HA, but it failed with an error.

From the network tab:

```

{

"data": {

"workflowStatus": {

"status": "Error",

"error": "An unknown error occurred"

}

}

}

```

Background

Initially, I attempted the conversion but discarded the changes because renaming the cluster (from "Postgres HA" to "database") didn't seem to work.

After discarding, I can no longer attempt the HA conversion again.

Has anyone encountered this issue or knows how to reset/retry the conversion?

Attachments

Solved

6 Replies

Status changed to Awaiting Railway Response Railway about 2 months ago


2 months ago

We weren't able to exactly reproduce this, but we believe we have merged a fix. Could you please try again?


Status changed to Awaiting User Response Railway about 2 months ago


brody

We weren't able to exactly reproduce this, but we believe we have merged a fix. Could you please try again?

injung
PROOP

2 months ago

Still not working.

Would it be possible for you to take a look at my service and see if there’s anything misconfigured or causing the issue?

Here is the link to my service:

https://railway.com/project/0893eafe-7e85-4f27-a62f-429fffb43ef1/service/b71c7560-db3c-4334-97d4-402b5ed06a8a/database?groupId=1b08b758-167d-4d71-aa4e-cf5959b30cef&environmentId=c3149ee6-0fa6-4b9e-9078-3de70f181f8d


Status changed to Awaiting Railway Response Railway about 2 months ago


2 months ago

Would we be able to try to initialize the HA Postgres ourselves?


Status changed to Awaiting User Response Railway about 2 months ago


brody

Would we be able to try to initialize the HA Postgres ourselves?

injung
PROOP

2 months ago

Sure. Since this is a preview environment, I can redeploy the Postgres instance (non-HA) after you identify the root cause.


Status changed to Awaiting Railway Response Railway about 2 months ago


2 months ago

Our engineer was able to upgrade the database to HA just fine, we believe you had a state frontend cached.


Status changed to Awaiting User Response Railway about 2 months ago


brody

Our engineer was able to upgrade the database to HA just fine, we believe you had a state frontend cached.

injung
PROOP

2 months ago

Thanks! I checked and was able to roll back to a non-HA instance.

Just a suggestion: would it be possible to keep applications pointing to the original Postgres instance during the HA conversion process for a safer migration? Then users could switch environment variables after everything is fully set up.

Otherwise, it seems like some downtime is unavoidable during the transition (although changes can technically be discarded manually).


Status changed to Awaiting Railway Response Railway about 2 months ago


Status changed to Solved injung about 2 months ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...