
On Mon, Jan 31, 2022 at 7:29 PM Nathanaƫl Blanchet <blanchet@abes.fr> wrote:
it doesn't seem to exist:
image: ba2efe1a-8b83-4406-8711-7120b4bd11d0
- 08966754-0bb6-4c88-9ad6-35d6242fa380 status: OK, voltype: LEAF, format: RAW, legality: LEGAL, type: PREALLOCATED, capacity: 219982856192, truesize: 219982856192 Is this the entire output? I assume not
And checking what the chain looks like there.
In theory it's possible to remove them from the database, but the relationships between the images would need to be fixed as well, as both images you mentioned have children
okay, tell me how to remove them from the DB please.
you can remove it using the image_guid, please check the a snapshot with their vm_snapshot_id does not exist in the snapshots table. image 109fac1e-c2e3-4ba6-9867-5d1c94d3a447 is the child of 60087f63-6237-4419-a5dd-9a48c84c1c43 which is going to be removed, so the chain needs to be fixed by updating the parent to 379db97c-bfe1-4804-9b1f-576050efdcd3 which is the parent of 60087f63-6237-4419-a5dd-9a48c84c1c43, and would be something like this: UPDATE images SET parentid = '379db97c-bfe1-4804-9b1f-576050efdcd3' WHERE image_guid = '109fac1e-c2e3-4ba6-9867-5d1c94d3a447'; of course this should done carefully after backing up the database