Bug 907326 - Server details shows a reference to VM's still - "Max free Memory for scheduling new VMs"
Summary: Server details shows a reference to VM's still - "Max free Memory for schedul...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: rhsc
Version: 2.1
Hardware: All
OS: All
medium
medium
Target Milestone: ---
: ---
Assignee: Kanagaraj
QA Contact: Prasanth
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-02-04 06:25 UTC by Prasanth
Modified: 2016-04-18 10:05 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-09-23 22:25:37 UTC
Embargoed:

Attachments (Terms of Use)
screenshot of server details (72.10 KB, image/png)
2013-02-04 06:25 UTC, Prasanth 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 11854 0 None None None Never

Description Prasanth 2013-02-04 06:25:43 UTC 
Created attachment 692626 [details]
screenshot of server details

Description of problem:

Server details shows a reference to VM's still - "Max free Memory for scheduling new VMs". Is this intentional? If not, please remove this reference.

Version-Release number of selected component (if applicable):
rhsc-2.1.0-0.qa5

How reproducible: Always


Steps to Reproduce:
1. Select a server and see the "General" sub-tab
2.
3.
  
Actual results: 


Expected results:


Additional info: Screenshot attached.
Comment 3 Scott Haines 2013-02-06 20:48:52 UTC 
Per Feb-06 bug triage meeting, targeting for 2.1.0.
Comment 4 Kanagaraj 2013-02-07 17:15:37 UTC 
Patch sent to upstream: http://gerrit.ovirt.org/11854
Comment 5 Kanagaraj 2013-02-07 17:17:34 UTC 
"Max free Memory for scheduling new VMs" and "LIBVIRT Version" are removed.
Comment 6 Matt Mahoney 2013-02-27 19:40:45 UTC 
Verified. Stats for VMs and LIBVIRT are no longer present.
Comment 7 Scott Haines 2013-09-23 22:25:37 UTC 
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-1262.html
Note You need to log in before you can comment on or make changes to this bug.