Bug 828904 - Duplicate EAP server under JBossAS7 node
Summary: Duplicate EAP server under JBossAS7 node
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: JBoss Operations Network
Classification: JBoss
Component: UI
Version: JON 3.1.0
Hardware: Unspecified
OS: Unspecified
medium
unspecified
Target Milestone: ---
: JON 3.1.1
Assignee: RHQ Project Maintainer
QA Contact: Mike Foley
URL:
Whiteboard:
Depends On:
Blocks: as7-plugin
TreeView+ depends on / blocked
 
Reported: 2012-06-05 14:56 UTC by Viet Nguyen
Modified: 2012-08-20 16:20 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-08-20 16:20:11 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
screen shot (86.15 KB, image/png)
2012-06-05 14:56 UTC, Viet Nguyen
no flags Details

Description Viet Nguyen 2012-06-05 14:56:31 UTC
Created attachment 589551 [details]
screen shot

Description of problem:

While testing  https://bugzilla.redhat.com/show_bug.cgi?id=815889 a duplicate EAP server showed up under agent | JBossAS7 Standalone Servers.  
Both nodes let me manange the same EAP server. 

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

How reproducible:
I can't reproduce

Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Viet Nguyen 2012-06-05 16:01:36 UTC
1.  Clarification: the duplicate EAP server didn't just 'show up' as managed resource.  It showed up in Discovery queue after I already imported one.   I then imported it.

2. I can also add 2 of the same EAP6 (manual + autodiscovery).  Works as designed?

Comment 2 Heiko W. Rupp 2012-06-08 11:56:43 UTC
Did you set up the box with an older version of the plugin first and then upgrade - perhaps without purging the older plugin?

Comment 3 Charles Crouch 2012-06-11 14:27:09 UTC
Discussed with mfoley and he indicated this wasn't a blocker given libor's 
testing in this area.

Comment 4 Charles Crouch 2012-08-20 16:20:11 UTC
Closing this based on it not being reproducible. If anyone can reproduce this then please reopen.


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