RDO tickets are now tracked in Jira https://issues.redhat.com/projects/RDO/issues/
Bug 1006888 - horizon [Havana]: limit summary - ram usage appears in MB
Summary: horizon [Havana]: limit summary - ram usage appears in MB
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: RDO
Classification: Community
Component: python-django-horizon
Version: unspecified
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
: ---
Assignee: Matthias Runge
QA Contact: Ami Jeain
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-09-11 13:01 UTC by Dafna Ron
Modified: 2015-06-04 21:53 UTC (History)
4 users (show)

Fixed In Version: python-django-horizon-2013.2-0.14.rc1.el6ost
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-11-21 10:48:47 UTC
Embargoed:

Attachments (Terms of Use)
screen shot (160.05 KB, image/png)
2013-09-11 13:01 UTC, Dafna Ron 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Launchpad 1223856 0 None None None Never

Description Dafna Ron 2013-09-11 13:01:55 UTC 
Created attachment 796362 [details]
screen shot

Description of problem:

I think the UI should always have a human readable default and that the limit summary should show ram in GB not MB

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

python-django-horizon-2013.2-0.10b3.el6.noarch

How reproducible:

100%

Steps to Reproduce:
1. install Havana AIO.  
2. in the dashboard -> projects -> instances look at the limit summary 
3.

Actual results:

ram appears in MB 

Expected results:

ram should appear in GB

Additional info:
Comment 1 Dafna Ron 2013-09-11 13:02:21 UTC 
https://bugs.launchpad.net/horizon/+bug/1223856
Comment 2 Dafna Ron 2013-09-11 13:03:03 UTC 
sorry, this is in the overview tab, not the instances.
Comment 3 Matthias Runge 2013-09-23 09:33:24 UTC 
Happens in all other python-django-horizon packages, too.
Comment 4 Matthias Runge 2013-09-24 07:08:24 UTC 
https://review.openstack.org/#/c/47809/ was merged recently, so the fix will be included in rc1
Note You need to log in before you can comment on or make changes to this bug.