Bug 1017434 - Compare Metrics Broken for Group Metrics
Summary: Compare Metrics Broken for Group Metrics
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Operations Network
Classification: JBoss
Component: UI
Version: JON 3.2
Hardware: Unspecified
OS: Unspecified
high
urgent
Target Milestone: ER05
: JON 3.2.0
Assignee: Mike Thompson
QA Contact: Mike Foley
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-10-09 21:06 UTC by Mike Thompson
Modified: 2014-01-02 20:33 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-01-02 20:33:40 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
autogroup-compare (608.56 KB, image/png)
2013-11-07 15:41 UTC, Armine Hovsepyan
no flags Details

Description Mike Thompson 2013-10-09 21:06:33 UTC
Description of problem:
Compare metrics button pulls up 404 error for /resource/common/monitor/Visibility.do

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


How reproducible:
Always


Steps to Reproduce:
1. Click on autogroup such as CPU
2. click monitoring tab
3. click metrics subtab
4. Select a couple member resources 
5. Hit Compare button

Actual results:
Error message saying 404.


Expected results:
metrics comparison screen.

Additional Info:
This page is coming from portal.war so either the portal.war location naming changes or BZ 995541 - Removing AWT Threading related classes.

Comment 1 Mike Thompson 2013-10-24 21:23:35 UTC
This was due to the portal.war naming changes in BZ 1000065 (session shows signs of life during install).
 
This is fixed in master commit id: dee3ffc.

Cherry-picked to release/jon3.2.x as commit id: 43f068a

Comment 2 Simeon Pinder 2013-11-07 02:17:29 UTC
Moving to ON_QA for test with new brew build.

Comment 3 Armine Hovsepyan 2013-11-07 15:40:48 UTC
verified in er5

screen-shot attached (no control on compare page -> #951927)

thank you.

Comment 4 Armine Hovsepyan 2013-11-07 15:41:08 UTC
Created attachment 821218 [details]
autogroup-compare


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