UI errors & volume stuck migrating to current region
Connecting a volume to a project with a different region started a migrating loop and bricked access to my volume
21 Replies
Project ID:
N/A
1270daf7-1f84-4e39-8444-3db245126f9c
i would say this is a pretty severe issue, now that i cant access my volume and have production downtime
!t
New reply sent from Help Station thread:
This thread has been escalated to the Railway team.You're seeing this because this thread has been automatically linked to the Help Station thread.
@Angelo - volume migration stuck
tagging team
New reply sent from Help Station thread:
Got an answer from the team, we checked the workflow and it's not stuck, however it is indeed taking a while, monitoring it.You're seeing this because this thread has been automatically linked to the Help Station thread. New reply sent from Help Station thread:
Jack, do you see that your volumes are migrated now? You should see it completed.You're seeing this because this thread has been automatically linked to the Help Station thread.
Appears to still be migrating
cc @Jack for ack
Reloaded a few more times and same message in every spot
Gotcha, where are you migrating to, the region?
east
from
volume was already on East but attached it to a west service
Wdym
Oh
production env running on East, filebrowser template deployed on west so I could move the files to s3
Gotcha, from our POV the migration is done, but the UI is showing it's not, trying to fix
sounds good, thank you!