Hi community,
We've encountered problem with virtual machines migrated from RHV(4.4.9.5-0.1.el8ev)
to oVirt (4.5.4-1.el8) using data domain.
When we create snapshot on migrated VM (in oVirt), we see that snapshot has same id as
"Active VM" snapshot and disk in illegal status. (we see that in web ui).
Meanwhile in database "engine" id's are different. And vdsm-tool shows that
there's only one snapshot in status "LEGAL".
engine=# select
image_guid,parentid,imagestatus,vm_snapshot_id,volume_type,volume_format,active from
images where image_group_id='12a8999f-3f6e-4377-8378-40370aa68d3f';
image_guid | parentid | imagestatus
| vm_snapshot_id | volume_type | volume_format | active
--------------------------------------+--------------------------------------+-------------+--------------------------------------+-------------+---------------+--------
5cf5a41d-7236-4c41-ae9c-7c6359210db6 | 6d9cc470-d66f-4e68-a0aa-6e8985f392b0 | 1
| 88d91f15-26ad-48c1-91ec-422c1c04e79b | 2 | 4 | t
6d9cc470-d66f-4e68-a0aa-6e8985f392b0 | 00000000-0000-0000-0000-000000000000 | 4
| a47261da-4ebb-42e3-a74a-0882f8e27c73 | 2 | 4 | f
(2 rows)
vdsm-tool dump-volume-chains 5e88e116-fb90-41ce-b9c3-01ccb9302b16 | grep
12a8999f-3f6e-4377-8378-40370aa68d3f -A 10
image: 12a8999f-3f6e-4377-8378-40370aa68d3f
- 6d9cc470-d66f-4e68-a0aa-6e8985f392b0
status: OK, voltype: LEAF, format: COW, legality: LEGAL, type: SPARSE,
capacity: 214748364800, truesize: 121198608384
We know how to fix this using database commands. But when we create snapshot , it happens
again. Question is how to prevent that?
Thank you.
Show replies by thread