#copy volume didn't work?

24 messages · Page 1 of 1 (latest)

frank crypt
#

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

clear spindleBOT
#

Project ID: 004e54e7-64a6-467d-960d-379e6d29e925,2665b49c-4fab-405a-a4c2-4983422dad1f

woven dawn
#

looks like it was canceled while it was in the queued state, you didnt cancel it?

frank crypt
#

no

#

but I opened the PR environment before it deployed the changes

#

anyway i'll just open a new PR

#

so yeah it happened again

#

env id: aff764f6-47f3-46bb-bef1-5267252ea99d

woven dawn
#

what happens if you disable copy volume data?

frank crypt
#

it probably works but i need copy volume data

woven dawn
#

volume voluma data is beta

frank crypt
#

thats why im reporting it

woven dawn
#

for sure, just saying it would be unwise to put yourself into a position where you need a beta feature

woven dawn
#

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

woven dawn
#

fix has been in place, let me know if you see the missing deployment issue again

frank crypt
#

will try it out

frank crypt
woven dawn
#

for Notus API?

frank crypt
#

oops i closed the PR kekw

#

i'll enable the copy volume again and create another PR

woven dawn
#

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.

woven dawn
#

hey @frank crypt - 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