a year ago
Hi Railway team,
believe our Postgres service was auto-migrated to Railway Metal, and we're now seeing this error on deploy:
Deployment failed during the pre-deploy process Volume migration failedOur situation:
- The volume
committee-volumeis still active and mounted - The region is EU West (Amsterdam) [Metal (NEW)]
- Grafana and other services are still pulling and writing data, so the old container is functioning
- We have not redeployed or rolled back yet
- We've taken a full backup via
.sqlexport
Can you please advise:
- Whether this volume can be safely remounted
- If a redeploy now would orphan or reset the volume
- Whether we can rollback to the pre-migration state manually
Project: Meticulous Creation
Database Image: ghcr.io/railwayapp-templates/postgres-ssl:16
Volume: committee-volume
Status: Data still flowing through other services
1 Replies
a year ago
Heya, so, your migration failed, and we kept the old deploy up.
I know the UI is a bit confusing but your data is safe; you can redeploy the service, and we'll migrate it at another time.
Sorry for the impact !
Best,
Nico
Status changed to Awaiting User Response Railway • 12 months ago
10 months ago
This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!
Status changed to Solved Railway • 10 months ago