Bug 1432493 - RESTAPI get diskssnapshots of a VM imported to upgraded DC - qcow_version field does not appear
Summary: RESTAPI get diskssnapshots of a VM imported to upgraded DC - qcow_version fie...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: BLL.Storage
Version: 4.1.1.4
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ovirt-4.1.2
: 4.1.2
Assignee: Maor
QA Contact: Avihai
URL:
Whiteboard:
Depends On: 1430447
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-03-15 14:09 UTC by Avihai
Modified: 2017-05-23 08:14 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2017-05-23 08:14:03 UTC
oVirt Team: Storage
Embargoed:
rule-engine: ovirt-4.1+


Attachments (Terms of Use)
engine , vdsm , test_timeline , restAPI get (506.94 KB, application/x-gzip)
2017-03-15 14:09 UTC, Avihai
no flags Details


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 74008 0 master MERGED core: Remove compat from OVF. 2017-03-26 16:20:45 UTC
oVirt gerrit 74641 0 ovirt-engine-4.1 MERGED core: Remove compat from OVF. 2017-03-27 09:05:52 UTC
oVirt gerrit 75374 0 master POST core: Set qcow compat for floating QCOW volumes. 2017-04-13 08:46:18 UTC
oVirt gerrit 75514 0 ovirt-engine-4.1 MERGED core: Set qcow compat for floating QCOW volumes. 2017-04-13 14:15:20 UTC

Description Avihai 2017-03-15 14:09:15 UTC
Created attachment 1263344 [details]
engine , vdsm , test_timeline , restAPI get

Description of problem:
The diskssnapshots of a VM(with disk+snapshot) that was:
1. VM create on 4.0 DC with disk+snapshots
2. exported to export domain 
3. VM removed 
4. VM imported to a DC in 4.1

qcow_version field does not appear !  

Checked via RESTAPI get to:
ovirt-engine/api/storagedomains/<sd_id>/disksnapshots

Version-Release number of selected component (if applicable):
Engine:
ovirt-engine-4.1.1.4-0.1.el7.noarch
VDSM:
4.19.6-1

How reproducible:
100%

Steps to Reproduce:
1. Create DC + cluster on v3

2. Create a VM with thin disk and create 5 snapshots 
-> checking qcow_version via ovirt-engine/api/storagedomains/<sd_id>/disksnapshots  
->I see qcow_version 2 as expected

3. Create export domain on v3 (4.0) DC
4. Export VM to export domain
5. Upgrade cluster &DC to version 4
6. Import the VM and verify disk&disksnapshots images version 0.10
   

Actual results:
Checking via restAPI diskssnapshots of the upgraded storage domain I DO NOT see any qcow_version field at all !!   

Expected results:
Checking via restAPI diskssnapshots of the upgraded storage domain I should see any qcow_version field as before the VM import .


Additional info:
path checked same as before import to see qcow_version details on disksnapshots:
https://storage-ge-04.scl.lab.tlv.redhat.com/ovirt-engine/api/storagedomains/d6c00916-f5f3-425f-8ff1-cfcfe56d61e5/disksnapshots

Comment 1 Maor 2017-03-15 14:27:45 UTC
This will be solved as part of BZ1430447
each import whether from export domain or unregistered entities will be queried with the storage domain through VDSM getQemuImgInfo for its qcow version.
Mean while the volume can be amended using the amend operation.

Comment 2 Maor 2017-04-13 08:45:17 UTC
(In reply to Maor from comment #1)
> This will be solved as part of BZ1430447
> each import whether from export domain or unregistered entities will be
> queried with the storage domain through VDSM getQemuImgInfo for its qcow
> version.

This also includes unregistered QCOW disks that will be registered to the setup.

Comment 3 Allon Mureinik 2017-04-13 09:16:08 UTC
Maor - if https://gerrit.ovirt.org/#/c/75374/ is part of the fix to this bugs, shouldn't it be moved back to POST, as it's not merged yet?

Comment 4 Maor 2017-04-13 11:04:45 UTC
(In reply to Allon Mureinik from comment #3)
> Maor - if https://gerrit.ovirt.org/#/c/75374/ is part of the fix to this
> bugs, shouldn't it be moved back to POST, as it's not merged yet?

yes, moving to post

Comment 5 Avihai 2017-04-27 08:25:42 UTC
verified on 4.1.2


Note You need to log in before you can comment on or make changes to this bug.