2 years ago
project id: 004e54e7-64a6-467d-960d-379e6d29e925
env id: 2665b49c-4fab-405a-a4c2-4983422dad1f
so i enabled copy volume data and it seems that my timescaledb database got in a weird state where it tried to deploy but removed the deploy afterward
26 Replies
2 years ago
looks like it was canceled while it was in the queued state, you didnt cancel it?
2 years ago
no
2 years ago
but I opened the PR environment before it deployed the changes
2 years ago
anyway i'll just open a new PR
2 years ago
so yeah it happened again
2 years ago
env id: aff764f6-47f3-46bb-bef1-5267252ea99d
2 years ago
what happens if you disable copy volume data?
2 years ago
it probably works but i need copy volume data
2 years ago
volume voluma data is beta
2 years ago
thats why im reporting it
2 years ago
for sure, just saying it would be unwise to put yourself into a position where you need a beta feature
2 years ago
follow up, I believe I know what the issue is, and if so, we have a fix in the works, funny enough if it's what I think this issue is, it doesn't have to do with copy volume data, although I could eat my words, we will have to wait and see
2 years ago
fix has been in place, let me know if you see the missing deployment issue again
2 years ago
will try it out
2 years ago
got a failed to create deployment
https://railway.com/project/004e54e7-64a6-467d-960d-379e6d29e925/service/1bff3ff4-6b65-4182-96cf-b7b676b48a1c?environmentId=c78a6765-b507-48e8-946c-9bb4d1931daf
2 years ago
for Notus API?
2 years ago
timescaledb
2 years ago
oops i closed the PR <:kekw:788259314607325204>
2 years ago
i'll enable the copy volume again and create another PR
2 years ago
here it is
2 years ago
okay now this is a completely different error than it was the first time, so the initial issue was solved.
i'll add this thread to our ticket for the current error, in the mean time you would need to disable the beta feature unfortunately.
2 years ago
Hello!
We're acknowledging your issue and attaching a ticket to this thread.
We don't have an ETA for it, but, our engineering team will take a look and you will be updated as we update the ticket.
Please reply to this thread if you have any questions!
2 years ago
🛠️ The internal ticket Error creating PR Env with Copy Volume Data has been marked as in progress.
2 years ago
✅ The internal ticket Error creating PR Env with Copy Volume Data has been marked as completed.
2 years ago
hey @ThallesComH - we believe to have identified the issue and implemented a fix for it, please re-enable and let me know if you see the issue again
2 years ago
forgot to reply, i'll give it a retry