1:25 p.m.
The bug you mentioned was fixed in 4.5.2.2. But to clarify the issue
that's fixed: The fix is for a situation where a snapshot removal
failed for whatever reason, but the volume was removed in vdsm and
remains present in the engine's database. Without the fix, attempting
to remove the snapshot again would fail.
Is this the scenario you are facing now?
There is another question of why the snapshot removal failed
initially, and I did not get logs with this information (although it
could be due to network issues)
On Fri, Aug 26, 2022 at 7:19 PM Giorgio Biacchi <giorgio(a)di.unimi.it> wrote:
Hi,
I filed a bug about this last year...
https://bugzilla.redhat.com/show_bug.cgi?id=1948599
We've dome some tests with vProtect after the leatest Ovirt release
4.5.2.4-1.el8 but we still have problems with snapshots removal and
disks left in locked or illegal state.
To bring back a disk from illegal state we live migrate the disk(s) to
another data domain. After this the snapshots are back to legal and can
be removed from the UI. This is pratical only for VMs with small disks.
Sadly one of the VMs we have problems with has a 2.5Tb disk attached :(
Hope this get solved soon.
Regards
Il 25/08/2022 10:26, Jirka Simon ha scritto:
> Hello Sven,
>
> Please do you have any details about it? Like bug report od knowledge
> base or article ? We have ovit and vprotect as well and our troubles
> started after last update of ovirt 4.4 ( frozen vm with snapshot crating
> job, then after unlock some snapshots is not possible to delete.) And
> now I'm preparing upgrade to 4.5.2 Yesterday we upgraded vProtect to the
> latest version.
>
> Thank you for any detail.
>
>
> Jirka
>
> On 8/24/22 15:20, Sven Jansen via Users wrote:
>> We are currently sitting on a not really working backup solution.
>> oVirt 4.5.x has constant issues removing snapshots, same like OP.
>> vProtect with Snapshots has issues with oVirt deleting snapshots.
>> vProtect 5.1 has broken CBT with oVirt 4.5.x.
>>
>> vProtect support tells us that the snapshot issues is in oVirt (true)
>> and CBT is a preview feature not really supported. So currently
>> vProtect 5.1 and oVirt 4.5 is a no go solution. We are thinking going
>> to xcp-ng due to constant issues with oVirt and or vProtect.
>> _______________________________________________
>> Users mailing list -- users(a)ovirt.org
>> To unsubscribe send an email to users-leave(a)ovirt.org
>> Privacy Statement: https://www.ovirt.org/privacy-policy.html
>> oVirt Code of Conduct:
>> https://www.ovirt.org/community/about/community-guidelines/
>> List Archives:
>>
https://lists.ovirt.org/archives/list/users@ovirt.org/message/V7VSQLOGJDT...
>>
> _______________________________________________
> Users mailing list -- users(a)ovirt.org
> To unsubscribe send an email to users-leave(a)ovirt.org
> Privacy Statement: https://www.ovirt.org/privacy-policy.html
> oVirt Code of Conduct:
> https://www.ovirt.org/community/about/community-guidelines/
> List Archives:
>
https://lists.ovirt.org/archives/list/users@ovirt.org/message/FMK2Z5B5K7Y...
>
--
gb
PGP Key: http://pgp.mit.edu/
Primary key fingerprint: C510 0765 943E EBED A4F2 69D3 16CC DC90 B9CB 0F34
_______________________________________________
Users mailing list -- users(a)ovirt.org
To unsubscribe send an email to users-leave(a)ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/users@ovirt.org/message/K5P7G25WSOU...