Bug 1504608 - Image from glance shows size 1024 MB instead of 1 GB when size is exactly 1073741824 B
Summary: Image from glance shows size 1024 MB instead of 1 GB when size is exactly 107...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: Frontend.WebAdmin
Version: 4.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ovirt-4.2.0
: ---
Assignee: Allon Mureinik
QA Contact: Petr Matyáš
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-10-20 10:14 UTC by Petr Matyáš
Modified: 2017-12-20 11:37 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2017-12-20 11:37:41 UTC
oVirt Team: Storage
Embargoed:
rule-engine: ovirt-4.2+


Attachments (Terms of Use)
screenshot (294.89 KB, image/png)
2017-10-20 10:14 UTC, Petr Matyáš
no flags Details


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 83055 0 master MERGED webadmin: DiskSizeRender lower bound 2017-10-22 10:29:32 UTC

Description Petr Matyáš 2017-10-20 10:14:27 UTC
Created attachment 1341186 [details]
screenshot

Description of problem:
I have some images in glance that have size exactly 1 GB (1073741824 B) for those images UI under storage -> images shows 1024 MB instead of 1 GB.
When this image is imported I can see 1 GB in Disks tab.

Version-Release number of selected component (if applicable):
ovirt-engine-4.2.0-0.0.master.20171013142622.git15e767c.el7.centos.noarch
also in 4.1 and probably older versions as well

How reproducible:
always

Steps to Reproduce:
1. have image in glance with size 1073741824 B
2. add that glance as a provider to RHV
3. open storage -> images for this glance

Actual results:
images with size 1073741824 B shows size 1024 MB

Expected results:
those images should show size 1 GB

Additional info:

Comment 1 Petr Matyáš 2017-10-30 17:11:53 UTC
Verified on ovirt-engine-4.2.0-0.0.master.20171029154613.git19686f3.el7.centos.noarch

Comment 2 Sandro Bonazzola 2017-12-20 11:37:41 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.


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