The f447cd4f-9ab3-489d-8c2a-b2e69456496f - "Auto-generated" snapshot should be deleted. After that, make sure the 5a58466b-1547-4346-a550-8590880b379e (Active VM) snapshot has an active=true flag.
*Regards,* *Shani Leviim* On Thu, Apr 16, 2020 at 9:33 PM David David <[email protected]> wrote: > snapshots in UI: > > Disk Snapshot ID > ===================================================== > 5a58466b-1547-4346-a550-8590880b379e - "Active VM" - has status "OK" > f447cd4f-9ab3-489d-8c2a-b2e69456496f - "Auto-generated" - has status > "Illegal" > ====================================================== > the "Disk Snapshot ID" with id 5a58466b-1547-4346-a550-8590880b379e > actually not present in LV > > error screenshot attached > > чт, 16 апр. 2020 г. в 18:20, Shani Leviim <[email protected]>: > >> Hi David, >> Can you share a screenshot of the error you're getting? >> And how the snapshots are presented on the ui? >> >> >> *Regards,* >> >> *Shani Leviim* >> >> >> On Thu, Apr 16, 2020 at 4:38 PM David David <[email protected]> wrote: >> >>> hi >>> >>> attempt to remove snapshot from UI results in an error >>> >>> I looked the LV through the lvs and did't find active snapshot ID, only >>> the base snapshot ID is present >>> >>> ovirt in database see 2 snapshots, but i have only one base image on >>> storage >>> >>> so, i must remove the active snapshot ID from db not the base image Id ? >>> >>> чт, 16 апр. 2020 г. в 13:58, Shani Leviim <[email protected]>: >>> >>>> Hi David, >>>> Sorry for the late reply. >>>> the volume_dump returned 1 occurrence of that image, while the query >>>> returned 2 occurrences. >>>> >>>> It seems that there's an image id with a description of 'Auto-generated >>>> for Live Storage Migration' which wasn't removed from the DB. >>>> Can you try to remove it from the UI? >>>> (If you claimed to remove it, try to remove it from the DB). >>>> >>>> >>>> *Regards,* >>>> >>>> *Shani Leviim* >>>> >>>> >>>> On Tue, Apr 7, 2020 at 7:45 PM David David <[email protected]> wrote: >>>> >>>>> vdsm-tool dump-volume-chains d17aa967-f7f7-4d9f-98e4-7022854da4f5 >>>>> >>>>> engine=# select * from images_storage_domain_view where >>>>> image_group_id='1844873e-45ef-4a2b-a991-2df6e92a3e2d'; >>>>> >>>>> output attached >>>>> >>>>> вт, 7 апр. 2020 г. в 19:47, Shani Leviim <[email protected]>: >>>>> >>>>>> Hi David, >>>>>> First, we need to compare the chain as it is seen by the engine and >>>>>> the host and see if there's a difference. >>>>>> Can you please share the output of the following? >>>>>> >>>>>> On the host: >>>>>> vdsm-tool dump-volume-chains <sd_id> >>>>>> >>>>>> On the engine: >>>>>> SELECT * >>>>>> FROM images_storage_domain_view images_storage_domain_view >>>>>> WHERE image_group_id = <image_group_id>; >>>>>> >>>>>> >>>>>> *Regards,* >>>>>> >>>>>> *Shani Leviim* >>>>>> >>>>>> >>>>>> On Tue, Apr 7, 2020 at 5:28 PM David David <[email protected]> >>>>>> wrote: >>>>>> >>>>>>> hello >>>>>>> >>>>>>> after removing "auto generated" snapshot, the vm snapshot became to >>>>>>> illegal status and in the "snapshot" tab also marked in illegal status >>>>>>> >>>>>>> now my vm is not booting >>>>>>> >>>>>>> but "vdsm-client Volume getInfo" shows the snapshot status is legal >>>>>>> >>>>>>> vdsm-client Volume getInfo \ >>>>>>> storagepoolID=00000000-0000-0000-0000-000000000000 \ >>>>>>> storagedomainID=d17aa967-f7f7-4d9f-98e4-7022854da4f5 \ >>>>>>> imageID=1844873e-45ef-4a2b-a991-2df6e92a3e2d \ >>>>>>> volumeID=f447cd4f-9ab3-489d-8c2a-b2e69456496f >>>>>>> >>>>>>> { >>>>>>> "status": "OK", >>>>>>> "lease": { >>>>>>> "path": "/dev/d17aa967-f7f7-4d9f-98e4-7022854da4f5/leases", >>>>>>> "owners": [], >>>>>>> "version": null, >>>>>>> "offset": 132120576 >>>>>>> }, >>>>>>> "domain": "d17aa967-f7f7-4d9f-98e4-7022854da4f5", >>>>>>> "capacity": "21474836480", >>>>>>> "voltype": "LEAF", >>>>>>> "description": "None", >>>>>>> "parent": "00000000-0000-0000-0000-000000000000", >>>>>>> "format": "RAW", >>>>>>> "generation": 1, >>>>>>> "image": "1844873e-45ef-4a2b-a991-2df6e92a3e2d", >>>>>>> "uuid": "f447cd4f-9ab3-489d-8c2a-b2e69456496f", >>>>>>> "disktype": "DATA", >>>>>>> "legality": "LEGAL", >>>>>>> "mtime": "0", >>>>>>> "apparentsize": "21474836480", >>>>>>> "truesize": "21474836480", >>>>>>> "type": "PREALLOCATED", >>>>>>> "children": [], >>>>>>> "pool": "", >>>>>>> "ctime": "1530472945" >>>>>>> } >>>>>>> >>>>>>> how to fix the problem? >>>>>>> _______________________________________________ >>>>>>> Users mailing list -- [email protected] >>>>>>> To unsubscribe send an email to [email protected] >>>>>>> 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/[email protected]/message/JSYMY4QG2HSPVITAX7QSVZDZ4HJDLN4W/ >>>>>>> >>>>>>
_______________________________________________ Users mailing list -- [email protected] To unsubscribe send an email to [email protected] 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/[email protected]/message/R6NNKRX4NCOQW4W2IO4GJYKY5IXEBN4H/
