Bug 1731245

Summary: Wrong disk size of managed block device disk shown when virtual machine: Bytes instead of gigabytes
Product: [oVirt] ovirt-engine Reporter: Mathias Schwenke <msch>
Component: Frontend.WebAdminAssignee: Eyal Shenitzky <eshenitz>
Status: CLOSED CURRENTRELEASE QA Contact: Shir Fishbain <sfishbai>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 4.3.4.3CC: aefrat, bugs, frolland, tnisan
Target Milestone: ovirt-4.3.6Flags: pm-rhel: ovirt-4.3+
pm-rhel: ovirt-4.4+
Target Release: 4.3.6.3   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: ovirt-engine-4.3.6.3 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-09-26 19:43:22 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
oVirt manager: edit virtual machine: disk size shown in bytes
none
Verified none

Description Mathias Schwenke 2019-07-18 18:21:02 UTC
Description of problem: Editing a virtual machine, disk size of managed block device disk (cinderlib, ceph) is shown in bytes instead of gigabytes. 


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

Comment 1 Tal Nisan 2019-07-22 14:25:13 UTC
Please attach a screenshot

Comment 2 Mathias Schwenke 2019-07-22 14:36:30 UTC
Created attachment 1592605 [details]
oVirt manager: edit virtual machine: disk size shown in bytes

Comment 5 Shir Fishbain 2019-08-25 14:30:50 UTC
Verified
disk size is shown in gigabytes 

ovirt-engine-4.3.6.3-0.1.el7.noarch
vdsm-4.30.25-1.el7ev.x86_64

Comment 6 Shir Fishbain 2019-08-25 14:33:02 UTC
Created attachment 1607853 [details]
Verified

Comment 7 Sandro Bonazzola 2019-09-26 19:43:22 UTC
This bugzilla is included in oVirt 4.3.6 release, published on September 26th 2019.

Since the problem described in this bug report should be
resolved in oVirt 4.3.6 release, it has been closed with a resolution of CURRENT RELEASE.

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