Bug 1129055 - Charts are corrupted after redraw
Summary: Charts are corrupted after redraw
Keywords:
Status: NEW
Alias: None
Product: RHQ Project
Classification: Other
Component: Core UI
Version: 4.9
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified vote
Target Milestone: ---
: ---
Assignee: RHQ Project Maintainer
QA Contact: Mike Foley
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-08-12 07:52 UTC by Yulia
Modified: 2014-10-13 11:43 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:


Attachments (Terms of Use)

Description Yulia 2014-08-12 07:52:13 UTC
Description of problem:


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. Display chart for several metrics 
2.Click redraw several times
3.

Actual results:
Sometimes some charts are empty with text "No metric data available" despite these charts were OK a seconds ago. If click redraw again, these charts are OK, but another ones are empty.
- Some charts may have a pink background after redraw. It becomes white after the next redraw
- Some charts may have the same content whereas corresponding metrics values differ

Expected results:
Selected metrics are charted separately. All charts are not empty (measurements data for selected metrics must exist, of course).
Charts don't change when redrawing them (the only change may be a new data collected and displayed)

Additional info:

Comment 1 Yulia 2014-08-12 08:01:08 UTC
There are several metrics on several resources from the same auto-group which have been collected some time (measurements values are present)
Reproduce: rarely

Comment 2 Heiko W. Rupp 2014-08-12 08:06:26 UTC
I see that you are on 4.9 - do you have a chance to re-test this on 4.12? I believe we fixed some charting issue with autogroups (and a lot of charting issues in total).

Comment 3 Yulia 2014-08-12 08:10:46 UTC
Unfortunatly, I don't have chance to re-test this on RHQ 4.12.


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