Bug 971649
| Summary: | d3 Graph High values are sometimes too large by quite a bit | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Other] RHQ Project | Reporter: | Mike Thompson <mithomps> | ||||||
| Component: | Core UI | Assignee: | Mike Thompson <mithomps> | ||||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Mike Foley <mfoley> | ||||||
| Severity: | high | Docs Contact: | |||||||
| Priority: | high | ||||||||
| Version: | 4.7 | CC: | hrupp | ||||||
| Target Milestone: | --- | ||||||||
| Target Release: | RHQ 4.9 | ||||||||
| Hardware: | Unspecified | ||||||||
| OS: | Unspecified | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2014-03-26 08:31:38 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: | |||||||||
| Attachments: |
|
||||||||
Created attachment 757984 [details]
graph showing erroneous max value
Created attachment 757985 [details]
json error raw data
The graphs have changed much since this BZ. In fact, the only place you can see this legend is on a wide portlet and inventory detail summary graph. I have verified this fix in file system resources of latest build. Bulk closing now that 4.10 is out. If you think an issue is not resolved, please open a new BZ and link to the existing one. |
Description of problem: Some graphs that show the legend at the right with min, max, avg have an erroneous value in the max. Looks like an error of 100x in some highs. Instead of a 9Gb max it is a 900Gb max. Reproduce: Take a look at the file system graphs for a single hard disk. An error in org.rhq.enterprise.gui.coregui.client.inventory.common.charttype.MetricGraphData#normalizeUnitsAndValues private MeasurementNumericValueAndUnits normalizeUnitsAndValues(double value, MeasurementUnits measurementUnits) { MeasurementNumericValueAndUnits newValue = MeasurementConverterClient.fit(value, measurementUnits); MeasurementNumericValueAndUnits returnValue; // adjust for percentage numbers if (measurementUnits.equals(MeasurementUnits.PERCENTAGE)) { returnValue = new MeasurementNumericValueAndUnits(newValue.getValue() * 100, newValue.getUnits()); } else { returnValue = new MeasurementNumericValueAndUnits(newValue.getValue(), newValue.getUnits()); } return returnValue; } Which should work but needs further investigation why it does not.