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

Bug 1487182

Summary: When exporting a disk to Glance, the size shown is its "Virtual Size" but the title is "Actual Size".
Product: [oVirt] ovirt-engine Reporter: shani <sleviim>
Component: BLL.StorageAssignee: shani <sleviim>
Status: CLOSED CURRENTRELEASE QA Contact: Raz Tamir <ratamir>
Severity: low Docs Contact:
Priority: unspecified    
Version: 4.2.0CC: amureini, bugs, tnisan
Target Milestone: ovirt-4.2.0Flags: rule-engine: ovirt-4.2+
Target Release: ---   
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-12-20 11:05:06 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:
Attachments:
Description Flags
Column's title is "Actual Size", but the data is the disk's virtual size. none

Description shani 2017-08-31 11:52:28 UTC
Created attachment 1320559 [details]
Column's title is "Actual Size", but the data is the disk's virtual size.

Description of problem:
When exporting a disk image from storage > disks, the size shown at the disk's summery refers to the disk's "Virtual Size", although the column's title is "Actual Size". 

Version-Release number of selected component (if applicable):
4.2.0

How reproducible:
100%

Steps to Reproduce:
1. Export a disk from storage > disks
2. Look at the "Actual Size" column on disk's summery details. 

Actual results:
|Actual Size|
-------------
|10 GB      |

Expected results:
|Virtual Size|
--------------
|10 GB       |

Additional info:
-

Comment 1 Raz Tamir 2017-10-15 13:46:44 UTC
Verified on ovirt-engine-4.2.0-0.0.master.20171013142622.git15e767c.el7.centos

Comment 2 Sandro Bonazzola 2017-12-20 11:05:06 UTC
This bugzilla is included in oVirt 4.2.0 release, published on Dec 20th 2017.

Since the problem described in this bug report should be
resolved in oVirt 4.2.0 release, published on Dec 20th 2017, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.