Description of problem: When copying a thin provision nfs template to iscsi domain,the image group that is created on the block domain consists of one raw preallocated volume disk. on NFS domain the template consists of raw sparse logical volume. from terminal vdsClient: on NFS-> [root@camel-vdsb data-center]# vdsClient -s 0 getVolumeInfo $sduuid $spuuid $imuuid `vdsClient -s 0 getVolumesList $sduuid $spuuid $imuuid` status = OK domain = 1b2dcee9-bcb1-4b80-8e7f-eaa4fc659c1a capacity = 4294967296 voltype = SHARED description = Active VM parent = 00000000-0000-0000-0000-000000000000 format = RAW image = 4158dea2-9c92-4167-a65f-bde633364745 uuid = ab488d9f-fa43-4b67-bb1a-7e0405c3e652 disktype = 2 legality = LEGAL mtime = 1401007275 apparentsize = 4294967296 truesize = 24576 type = SPARSE children = [] pool = ctime = 1401007275 on ISCSI-> [root@camel-vdsb data-center]# vdsClient -s 0 getVolumeInfo $sduuid $spuuid $imuuid `vdsClient -s 0 getVolumesList $sduuid $spuuid $imuuid` status = OK domain = ceb80915-8207-4ebe-9c45-458676fdf223 capacity = 4294967296 voltype = SHARED description = parent = 00000000-0000-0000-0000-000000000000 format = RAW image = 4158dea2-9c92-4167-a65f-bde633364745 uuid = ab488d9f-fa43-4b67-bb1a-7e0405c3e652 disktype = 2 legality = LEGAL mtime = 1401007365 apparentsize = 4294967296 truesize = 4294967296 type = PREALLOCATED children = [] pool = ctime = 1401007363 Version-Release number of selected component (if applicable): vdsm-4.14.7-3.el6ev.x86_64 rhevm-3.4.0-0.21.el6ev.noarch How reproducible: 100% Steps to Reproduce: Setup:have a shared dc with two domains(one nfs,one iscsi) 1.create vm+thin nfs disk-> create a template from this disk 2.copy template to iscsi domain Actual results: the web admin ui reports of a thin provision template(see image) Expected results: we should see both,or whatever makes sense Additional info:
Created attachment 899967 [details] wrong_disk_format
Currently, the storage properties are coupled to the disk entity, even if it has two different physical copies. In 3.6 we should refactor the disk BE to separate the logical properties from the storage ones. Tal - please make sure this RFE is filed.
(In reply to Allon Mureinik from comment #2) > Currently, the storage properties are coupled to the disk entity, even if it > has two different physical copies. > > In 3.6 we should refactor the disk BE to separate the logical properties > from the storage ones. > Tal - please make sure this RFE is filed. This is bug 1142762.
Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release.
Moving from 4.0 alpha to 4.0 beta since 4.0 alpha has been already released and bug is not ON_QA.
oVirt 4.0 beta has been released, moving to RC milestone.
Frankly. I don't see us ever getting to this. Closing. If anyone thinks this is important, please explain why and reopen.