Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 873142 - In "create a new virtual machine" dialog of virt-manager,unit of "Storage" is incorrect
In "create a new virtual machine" dialog of virt-manager,unit of "Storage" is...
Status: CLOSED ERRATA
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: virt-manager (Show other bugs)
6.4
Unspecified Unspecified
medium Severity medium
: rc
: ---
Assigned To: Martin Kletzander
Virtualization Bugs
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2012-11-05 03:57 EST by tingting zheng
Modified: 2013-11-21 15:38 EST (History)
9 users (show)

See Also:
Fixed In Version: virt-manager-0.9.0-19.el6
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2013-11-21 15:38:39 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2013:1646 normal SHIPPED_LIVE virt-manager bug fix update 2013-11-20 16:53:27 EST

  None (edit)
Description tingting zheng 2012-11-05 03:57:47 EST
Description
In "create a new virtual machine" dialog of virt-manager,unit of "Storage" is incorrect,it shows as Gb instead of GB.

Version
virt-manager-0.9.0-15.el6.x86_64
libvirt-0.10.2-6.el6.x86_64

How reproducible:
100%

Steps to Reproduce
1.Launch virt-manager.

2.Click "New" to create a virtual machine,input name,choose "Import existing disk image",click forward.

3.Input the existing storage path,eg:/var/lib/libvirt/images/qcow2.img,click forward.

4.Choose memory and cpu,click forward.

5.On the dialog,you can see the unit of "Storage" is Gb.

Actual results:
As step5 shows.

Expected results:
The unit of "Storage" shows as GB.

Additional info:
Comment 3 Martin Kletzander 2013-03-14 10:15:24 EDT
Already fixed in RELEASE-0.9.0-1-104-gb7a533a:

commit b7a533a45116bea4d156f9cde6dd934a1d2e28ed
Author: Cole Robinson <crobinso@redhat.com>
Date:   Sun Jan 29 21:51:07 2012 -0500

    create: s/Gb/GB/ for storage units
Comment 11 luxin 2013-08-02 04:17:13 EDT
I can reproduce this bug:

Version:
virt-manager-0.9.0-15.el6.x86_64
libvirt-0.10.2-7.el6.x86_64(libvirt-0.10.2-6.el6.x86_64 has been deleted)

Steps for Reproduce:
1.Launch #virt-manager.
2.Click "New" to create a virtual machine,input name,choose "Import existing disk image",click forward.
3.Input the existing storage path, click forward.
4.Choose memory and cpu,click forward.
5.On the step5 dialog, see the unit of "Storage".

Result:
Storage: Gb

Verify:
libvirt-0.10.2-21.el6.x86_64
virt-manager-0.9.0-19.el6.x86_64

Steps for Verify:
1.Launch #virt-manager.
2.Click "New" to create a virtual machine,input name,choose "Import existing disk image",click forward.
3.Input the existing storage path, click forward.
4.Choose memory and cpu,click forward.
5.On the step5 dialog, see the unit of "Storage".

Result:
Storage: GB
Comment 15 errata-xmlrpc 2013-11-21 15:38:39 EST
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

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

http://rhn.redhat.com/errata/RHBA-2013-1646.html

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