+++ This bug was initially created as a clone of Bug #1070521 +++ Description of problem: The Outlier column always renders a value of zero due to a bug in MeasurementOOBManagerBean. The methods, * getHighestNOOBsForGroup * getHighestNOOBsForResource * getSchedulesWithOOBs all execute a query to fetch one hour data that is needed in order to compute outliers. That query is executed against the legacy one hour data table in the relational database; consequently, it always returns an empty result set. This in turn produces always produces outliers of zero. The above methods are also called to render the resource and group OOB Metrics portlet. I have reviewed the code the involved with Mike Thompson. I do not think that the portlets are affected by this because they do not use the outlier property in MeasurementOOBComposite. Mike please chime in here if I am wrong. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
We need to investigate the suspect metrics report and these values. There may be issues given what this says and also what Mike was showing me today.
Moving into ER05 as didn't make the ER04 cut.
master: 7ceb5f74938f720919c378a93ab82a0e66e56702 release/jon3.3.x: bc9b41d30ef73103771f9530c6ad3fbc99827eb2 Author: Lukas Krejci <lkrejci> Date: Mon Oct 13 13:34:44 2014 +0200 [BZ 1070521] Fixed retrieval of OOB datapoints. (cherry picked from commit 7ceb5f74938f720919c378a93ab82a0e66e56702)
Moving to ON_QA as available to test with the latest brew build: https://brewweb.devel.redhat.com//buildinfo?buildID=394734
Verified in ER05.