Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1432493

Summary: RESTAPI get diskssnapshots of a VM imported to upgraded DC - qcow_version field does not appear
Product: [oVirt] ovirt-engine Reporter: Avihai <aefrat>
Component: BLL.StorageAssignee: Maor <mlipchuk>
Status: CLOSED CURRENTRELEASE QA Contact: Avihai <aefrat>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 4.1.1.4CC: amureini, bugs, lveyde, mlipchuk, ylavi
Target Milestone: ovirt-4.1.2Keywords: TestOnly
Target Release: 4.1.2Flags: rule-engine: ovirt-4.1+
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-05-23 08:14:03 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Storage RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1430447    
Bug Blocks:    
Attachments:
Description Flags
engine , vdsm , test_timeline , restAPI get none

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