On one oVirt 4.3 farm I have three locked images I'd like to clear out. One is an ISO image, that somehow never completed the transfer due to a slow network. It's occupying little space, except in the GUI where it sticks out and irritates. I guess it would just be an update somewhere on the Postgress database to unlock it and have it deletable: But since the schema isn't documented, I'd rather ask here: How to I unlock the image? Two are left-overs from a snapshot that somehow never completed, one for the disk another for the RAM part. I don't know how my colleague managed to get into that state, but impatience/concurrency probably was a factor, a transient failure of a node could have been another. In any case the snapshot operation logically has been going on for weeks without any real activity, survived several restarts (after patches) of all nodes and the ME and shows no sign of disappearing voluntarily. Again, I'd assume that I need to clear out the snapshot job, unlock the images and then delete what's left. Some easy SQL and most likely a management engine restart afterwards... if you knew what you were doing (or there was an option in the GUI). So how do I list/delete snapshot jobs that aren't really running any more? And how do I unlock the images so I can delete them? Thanks for your help!
Hi Thomas, You can use unlock_entity.sh[1] to list the unlock entities and remove them. [1] https://www.ovirt.org/develop/developer-guide/db-issues/helperutilities.html *Regards,* *Shani Leviim* On Tue, Dec 15, 2020 at 10:45 AM <thomas@hoberg.net> wrote:
On one oVirt 4.3 farm I have three locked images I'd like to clear out.
One is an ISO image, that somehow never completed the transfer due to a slow network. It's occupying little space, except in the GUI where it sticks out and irritates. I guess it would just be an update somewhere on the Postgress database to unlock it and have it deletable: But since the schema isn't documented, I'd rather ask here: How to I unlock the image?
Two are left-overs from a snapshot that somehow never completed, one for the disk another for the RAM part. I don't know how my colleague managed to get into that state, but impatience/concurrency probably was a factor, a transient failure of a node could have been another.
In any case the snapshot operation logically has been going on for weeks without any real activity, survived several restarts (after patches) of all nodes and the ME and shows no sign of disappearing voluntarily.
Again, I'd assume that I need to clear out the snapshot job, unlock the images and then delete what's left. Some easy SQL and most likely a management engine restart afterwards... if you knew what you were doing (or there was an option in the GUI).
So how do I list/delete snapshot jobs that aren't really running any more? And how do I unlock the images so I can delete them?
Thanks for your help! _______________________________________________ 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/XHC5GNLOZO2WFE...
Thanks Shani, I had just found that myself and even managed to unlock and remove the images. Somehow the reference to https://ovirt.org/develop/developer-guide/ seems to not be available from the ovirt site navigation but now I have discovered it via another post here and found a treasure trove.
And I should have guessed, that this is only how trouble starts =:-O I immediately removed the locked snapshot image (actually they pretty much seemed to disappear by themselves as delete operations might have been pending) but the VM that was doing the snapshot, is still there, even if the disks are long gone. But there are still references in the VM to two (now gone) snapshot images with a status 'illegal' (because they don't exist anymore) that I cannot delete from the VM... without which I cannot delete the VM. Any idea how to fix that?
Unlocked the snapshot, deleted the VM... done! That was easiser than I thought. Thanks for your help in any case!
participants (2)
-
Shani Leviim -
thomas＠hoberg.net