2 years ago
Connecting a volume to a project with a different region started a migrating loop and bricked access to my volume
22 Replies
2 years ago
2 years ago
1270daf7-1f84-4e39-8444-3db245126f9c
2 years ago
i would say this is a pretty severe issue, now that i cant access my volume and have production downtime
2 years ago
2 years ago
!t
2 years ago
This thread has been escalated to the Railway team.
Status changed to Awaiting Railway Response brody • over 1 year ago
2 years ago
@angelo - volume migration stuck
2 years ago
tagging team
2 years ago
Got an answer from the team, we checked the workflow and it's not stuck, however it is indeed taking a while, monitoring it.
Status changed to Awaiting User Response Railway • over 1 year ago
2 years ago
Jack, do you see that your volumes are migrated now? You should see it completed.
2 years ago
Appears to still be migrating
2 years ago
cc @Jack for ack
2 years ago
2 years ago
Reloaded a few more times and same message in every spot
2 years ago
Gotcha, where are you migrating to, the region?
2 years ago
east
2 years ago
from
2 years ago
volume was already on East but attached it to a west service
2 years ago
Wdym
2 years ago
Oh
2 years ago
production env running on East, filebrowser template deployed on west so I could move the files to s3
2 years ago
Gotcha, from our POV the migration is done, but the UI is showing it's not, trying to fix
2 years ago
sounds good, thank you!
2 years ago
This thread has been marked as solved automatically due to a lack of recent activity. Please open a new thread if you require further assistance. Thank you!
Status changed to Solved Railway • over 1 year ago