Description of problem: When exporting a disk to an external glance provider the actual size of the disk is displayed as "<1". Version-Release number of selected component (if applicable): vdsm-4.17.10.1-0.el7ev.noarch rhevm-3.6.0.3-0.1.el6.noarch Libvirt: ------------------------------------ libvirt-client-1.2.17-13.el7.x86_64 libvirt-python-1.2.17-2.el7.x86_64 libvirt-daemon-driver-interface-1.2.17-13.el7.x86_64 libvirt-daemon-driver-storage-1.2.17-13.el7.x86_64 libvirt-daemon-1.2.17-13.el7.x86_64 libvirt-daemon-driver-nwfilter-1.2.17-13.el7.x86_64 libvirt-daemon-config-nwfilter-1.2.17-13.el7.x86_64 libvirt-daemon-driver-nodedev-1.2.17-13.el7.x86_64 libvirt-daemon-driver-secret-1.2.17-13.el7.x86_64 libvirt-daemon-driver-qemu-1.2.17-13.el7.x86_64 libvirt-daemon-kvm-1.2.17-13.el7.x86_64 libvirt-daemon-driver-network-1.2.17-13.el7.x86_64 libvirt-lock-sanlock-1.2.17-13.el7.x86_64 Qemu: ------------------------------------ qemu-kvm-tools-rhev-2.3.0-31.el7.x86_64 qemu-kvm-common-rhev-2.3.0-31.el7.x86_64 How reproducible: 100% Steps to Reproduce: 1. Created a VM with a 14g preallocated block disk 2. Started the VM and installed OS on the disk 3. Copied a 1.5g file to the disk on the os 4. Powered off the VM 5. Via the Disk Tab selected to export the disk to a Glance external provider >>>>> The actual size for the 14g disk with an OS installed on it and after having copied 1.5g of data to the disk is displayed as "<1" Actual results: actual size of the disk to be exported is "<1" Expected results: Additional info: See screen shot!
Created attachment 1093064 [details] engine, vdsm, server logs, screen shots Added logs and screen shot!
This bug is not marked for z-stream, yet the milestone is for a z-stream version, therefore the milestone has been reset. Please set the correct milestone or add the z-stream flag.
Actual size is reported correctly in the export image(s) prompt. Also, when the export operation is done, the image appears in the import images view under the Glance repository with its correct size. Verified using: rhevm-3.6.1.1-0.1.el6.noarch vdsm-4.17.12-0.el7ev.noarch
According to verification status and target milestone this issue should be fixed in oVirt 3.6.1. Closing current release.