a year ago
Connecting a volume to a project with a different region started a migrating loop and bricked access to my volume
2 Replies
a year ago
a year ago
1270daf7-1f84-4e39-8444-3db245126f9c
a year ago
i would say this is a pretty severe issue, now that i cant access my volume and have production downtime
a year ago
a year ago
!t
a year ago
This thread has been escalated to the Railway team.
Status changed to Awaiting Railway Response brody • over 1 year ago
a year ago
@angelo - volume migration stuck
a year ago
tagging team
a year 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
a year ago
Jack, do you see that your volumes are migrated now? You should see it completed.
a year ago
Appears to still be migrating
a year ago
cc @Jack for ack
a year ago
a year ago
Reloaded a few more times and same message in every spot
a year ago
Gotcha, where are you migrating to, the region?
a year ago
east
a year ago
from
a year ago
volume was already on East but attached it to a west service
a year ago
Wdym
a year ago
Oh
a year ago
production env running on East, filebrowser template deployed on west so I could move the files to s3
a year ago
Gotcha, from our POV the migration is done, but the UI is showing it's not, trying to fix
a year ago
sounds good, thank you!
a year 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