Bug 1010336 - Availability axes sometimes get messy when moving from Resource to Resource and changing timeframes
Summary: Availability axes sometimes get messy when moving from Resource to Resource a...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: RHQ Project
Classification: Other
Component: Core UI
Version: 4.10
Hardware: All
OS: All
unspecified
unspecified
Target Milestone: ER03
: RHQ 4.10
Assignee: Mike Thompson
QA Contact: Mike Foley
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-09-20 14:32 UTC by Mike Thompson
Modified: 2014-04-23 12:32 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-04-23 12:32:17 UTC
Embargoed:

Attachments (Terms of Use)
Availability graph messed up (193.62 KB, image/jpeg)
2013-09-20 14:36 UTC, Mike Thompson 		no flags Details
View All

Description Mike Thompson 2013-09-20 14:32:53 UTC 
Description of problem:
This looks to be the last of the bugs from the auto-refresh refactoring (so that page only refreshes the chart and not the whole page: https://bugzilla.redhat.com/show_bug.cgi?id=924725)

When moving between resources on the metrics page

Reproducibility:
Sometimes.

Steps to Reproduce
1) click to metrics tab on a Resource
2) Click to another resource in the tree
3) change the timeframe of the graphs say to 1h
4) click to another resource in the tree

Note that the availability axes are overwritten with 2 axes (the first one is not deleted when the second one is added). This bug was introduced from the lifecycle changes introduced from the bug mentioned above.
Comment 1 Mike Thompson 2013-09-20 14:36:36 UTC 
Created attachment 800521 [details]
Availability graph messed up
Comment 2 Mike Thompson 2013-09-23 21:31:44 UTC 
Checked into master commit id: abc2c82
Comment 3 Heiko W. Rupp 2014-04-23 12:32:17 UTC 
Bulk closing of 4.10 issues.

If an issue is not solved for you, please open a new BZ (or clone the existing one) with a version designator of 4.10.
Note You need to log in before you can comment on or make changes to this bug.