Bug 517352 - Incorrect number of CPU and RAM
Summary: Incorrect number of CPU and RAM
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Virtualization Tools
Classification: Community
Component: ovirt-server-suite
Version: unspecified
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Hugh Brock
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-08-13 15:20 UTC by Sylvain Desbureaux
Modified: 2014-01-20 14:39 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-01-20 14:39:18 UTC


Attachments (Terms of Use)

Description Sylvain Desbureaux 2009-08-13 15:20:47 UTC
Description of problem:
The number of CPU and RAM displayed in the front page of the hardware pool count also the CPUs and RAMs of the disabled (so unusable) ones.

Version-Release number of selected component (if applicable):
ovirt-build.noarch                    0.99-0.fc11 
ovirt-node-image.x86_64               1.0.2-0.fc11.20090812121135git5d11d54
ovirt-node-image-pxe.x86_64           1.0.2-0.fc11.20090812121135git5d11d54
ovirt-release.noarch                  0.99-1.fc10 
ovirt-server.noarch                   0.101-0.fc11.20090812115539git5db2ee4
ovirt-server-installer.noarch         0.101-0.fc11.20090812115539git5db2ee4


How reproducible:
Always

Steps to Reproduce:
1.Look at the front page of an Hardware pool and look at the number of CPU and RAM
2.go to the hosts page and disable one
3.Go back at the front page
  
Actual results:
The values for CPU and RAM are the same even if we have disabled one hosts


Expected results:
The value at the end should be the sum of the value of enabled hosts only


Additional info:

Comment 1 Cole Robinson 2014-01-20 14:39:18 UTC
This bugzilla product/component combination is no longer used: ovirt bugs are tracked under the bugzilla product 'oVirt'. If this bug is still valid, please reopen and set the correct product/component.


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