Bug 1285899

Summary:	Metric rollups for container providers are not properly determined
Product:	Red Hat CloudForms Management Engine	Reporter:	Federico Simoncelli <fsimonce>
Component:	C&U Capacity and Utilization	Assignee:	Federico Simoncelli <fsimonce>
Status:	CLOSED ERRATA	QA Contact:	Einat Pacifici <epacific>
Severity:	high	Docs Contact:
Priority:	high
Version:	5.5.0	CC:	cpelland, dron, fsimonce, jfrey, jhardy, jprause, obarenbo, srevivo
Target Milestone:	GA
Target Release:	5.6.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	container
Fixed In Version:	5.6.0.0	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:
Clones:	1287766 (view as bug list)		Environment:
Last Closed:	2016-06-29 15:12:37 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1321561
Bug Blocks:	1287766

Description Federico Simoncelli 2015-11-26 22:47:00 UTC

Description of problem:
Metric rollups of container nodes to the container provider are not properly determined:

- memory usage is not computed
- cores usage is computed using a simple average (instead of a weighted average on number of cores)

How reproducible:
100%

Steps to Reproduce:
1. add a container provider with metrics support

Actual results:
Daily/hourly metrics rollups for containers providers are not properly determined (see above)

Expected results:
Daily/hourly metrics rollups for containers providers should be properly computed.

Additional info:
These data are not yet visibile in the UI but since are stored in the database we need to get the computation right so that once the UI is added the values are correct.

Comment 1 Federico Simoncelli 2015-11-26 22:49:42 UTC

https://github.com/ManageIQ/manageiq/pull/5587

Comment 2 Oleg Barenboim 2015-11-28 18:26:49 UTC

https://github.com/ManageIQ/manageiq/pull/5587 has been merged

Comment 9 errata-xmlrpc 2016-06-29 15:12: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.

https://access.redhat.com/errata/RHBA-2016:1348