a month ago
Pressing Deploy after creating and mounting a volume pends for a couple minutes, then stops pending and shows the Deploy button again.
9 Replies
Attempting to create a Postgres instances with volumes on my staging environment by "syncing" from the production environment also fails to create and mount a volume.
Attachments
Status changed to Awaiting Railway Response Railway • about 1 month ago
a month ago
Apologies for the inconvienience.
Just to clarify are you trying to attach 2 volumes to a Postgres? They can only have one. Even if so, it should be caught earlier. Please confirm and I will flag internally. Feel free to give background/the why on the volumes - whether aiming to switch or have two.
Status changed to Awaiting User Response Railway • about 1 month ago
No, I am attempting to attach one volume. This happened when I created a new "staging" environment copied from "production". The initial creation failed to create volumes. The dashboard shows no indication that those services have volumes other than the console error seen above
a month ago
(snip)
Status changed to Awaiting Railway Response Railway • about 1 month ago
Feel free to create a volume for any of the three Postgres services on the staging environment. You should see the same error in the console when pressing Deploy
a month ago
Ok makes sense now, I am escalating to engineering. In the meantime please try this to resume service: delete and recreate the staging environment, or discard the current staged changes and re-add the volumes manually one at a time. Will update, apologies for inconvenience.
Status changed to Awaiting User Response Railway • about 1 month ago
a month 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 • 27 days ago