2 years ago
Hi there,
Since this morning, when we deploy a PR environment, the deployment fails because the services (Redis and Postgres) say they're "Pending migration to a new region". This takes upwards of 30 minutes each time with create a new PR environment.
When I click into the details, it says "You have a volume attached to this service which is currently being migrated to the US West region.". All of our infra is based in Singapore, so not sure what this is about? Are you busy with some migrations? Or is it perhaps a config issue on our end?
Thank you!
12 Replies
2 years ago
Can confirm I have seen this exact same thing, text saying the volume is migrating to the wrong region.
Status changed to Awaiting User Response Railway • over 1 year ago
2 years ago
Can confirm no manual migrations triggered.
Status changed to Awaiting Railway Response Railway • over 1 year ago
2 years ago
Latest PR Environment I deployed didn't recover like the others did, and now looks stuck (75mins) in this state.
2 years ago
In my case I was adding a volume to a service that was already in Singapore and got the exact same message as OP, this was several days ago and Charles brought it up in a #help thread, like OP their migration eventually completed as well.
2 years ago
FWIW, I've tried explicitly setting the region to asia-southeast1 in railway.json in our project root, but it didn't seem to solve the issue.
2 years ago
We shipped a fix just now so that volumes won't need to be migrated when you spin up new environments in a region. This should speed up the creation of PR environments.
We also addressed the misleading label suggesting that the volumes were being migrated to US West, as the migration was to Singapore in your case.
You can verify by closing and reopening a PR or verify when you open a new PR. Please let us know if anything doesn't look as expected.
Status changed to Awaiting User Response Railway • over 1 year ago
2 years ago
Can confirm, there is no longer a migration step when adding a volume to a service that is not in us-west.
However there is still a toast message that says the volume was migrated.
Status changed to Awaiting Railway Response Railway • over 1 year ago
2 years ago
PR Environments now deploy again. Thank you!
2 years ago
Can confirm, there is no longer a migration step when adding a volume to a service that is not in us-west.
However there is still a toast message that says the volume was migrated.
Thank you for confirming. We've created a ticket to address the toast message.
Status changed to Awaiting User Response Railway • over 1 year ago
2 years ago
PR Environments now deploy again. Thank you!
Thank you for confirming. I'll mark this as solved, but feel free to comment if you anything related to this going forward
.
Status changed to Solved christian • over 1 year ago