There was no manual database change, I meant calling the /finalize
endpoint can change the phase of a transfer and move it to an
incorrect state like happened in your case. In your scenario the
client is Veeam, but this is not their fault, but an issue in oVirt,
since we should not change the phase in such cases.
Let me know if manually removing the transfer helped.
On Mon, Aug 1, 2022 at 4:59 PM Diego Ercolani <diego.ercolani(a)ssis.sm> wrote:
In data lunedì 1 agosto 2022 15:55:56 CEST, Benny Zlotnik ha scritto:
> So looks like the transfer failed, but it was later finalized moving
> it from FINISHED_FAILURE to FINALIZING_SUCCESS, we have a bug to
> prevent clients from changing the transfer's status like this, fix
> should land in 4.5.3
When you talk "client" in this case I can assure you I didn't change the
DB
manually. But I don't know if Veeam did it.
Anyway thank you for the support
Diego