Hi,

You can use the DeleteImage tool [1], but it's first recommended to backup your engine.

To be on the safe side, here are some checks it's better to execute before deleting:

- In order to locate the illegal image, you can run this command on the host:
vdsm-tool dump-volume-chains <sd_id>

- It's also recommended to verify that the engine and vdsm are synced about that image, once you've found it, by running this command on the engine:
SELECT *
FROM images_storage_domain_view images_storage_domain_view
WHERE image_group_id = <image_group_id>;

[1]

DeleteImage tool:
SELECT DeleteImage('image-id');

DELETE
FROM images
WHERE image_guid = v_image_guid;

Regards,

Shani Leviim

On Wed, Apr 21, 2021 at 1:17 PM Giulio Casella <giulio@di.unimi.it> wrote:

I tried, with no luck. Giving "disk snapshot id" as a parameter to that
psql procedure nothing happened. Giving the "vm_snapshot_id" as found in
the "images" table made the snapshot disappear from the gui, but not
from the "images" table.

SO I decided to look into DeleteSnapshot procedure, that resolve as:

DELETE FROM snapshots WHERE snapshot_id = v_snapshot_id;

It only acts on the "snapshots" table, and not on the "image" table,
where the parentship between snapshots is still wrong.

How safe is to manually modify "images" table and set correct parentship?

On 20/04/2021 15:56, Shani Leviim wrote:
> Thanks, Ritesh.
>
> In order to delete that snapshot, run this command on psql:
> SELECT DeleteSnapshot('snapshot-id');
>
> *Regards,
> *
> *Shani Leviim
> *
>
>
> On Tue, Apr 20, 2021 at 3:25 PM Ritesh Chikatwar <rchikatw@redhat.com
> <mailto:rchikatw@redhat.com>> wrote:
>
> adding @Shani Leviim <mailto:sleviim@redhat.com>
>
> On Tue, Apr 20, 2021 at 5:35 PM Thomas Hoberg <thomas@hoberg.net
> <mailto:thomas@hoberg.net>> wrote:
>
> I have used these tools to get rid of snapshots that wouldn't go
> away any other way:
> https://www.ovirt.org/develop/developer-guide/db-issues/helperutilities.html
> <https://www.ovirt.org/develop/developer-guide/db-issues/helperutilities.html>
> _______________________________________________
> Users mailing list -- users@ovirt.org <mailto:users@ovirt.org>
> To unsubscribe send an email to users-leave@ovirt.org
> <mailto:users-leave@ovirt.org>
> Privacy Statement: https://www.ovirt.org/privacy-policy.html
> <https://www.ovirt.org/privacy-policy.html>
> oVirt Code of Conduct:
> https://www.ovirt.org/community/about/community-guidelines/
> <https://www.ovirt.org/community/about/community-guidelines/>
> List Archives:
> https://lists.ovirt.org/archives/list/users@ovirt.org/message/37K5J2X2OUDQKN5J3J7ISOV26FMTHCTY/
> <https://lists.ovirt.org/archives/list/users@ovirt.org/message/37K5J2X2OUDQKN5J3J7ISOV26FMTHCTY/>
>
>
> _______________________________________________
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-leave@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/LS3BUPQIVHQMG7I7C6IL7QTXJTJE7KCE/
>