Bug 920178

Summary:	[IPv6] EAP6 standalone contains DomainDeployment resource child when 2 EAP6 (Domain + Standalone) are imported on same agent
Product:	[JBoss] JBoss Operations Network	Reporter:	Libor Zoubek <lzoubek>
Component:	Plugin -- JBoss EAP 6	Assignee:	RHQ Project Maintainer <rhq-maint>
Status:	CLOSED EOL	QA Contact:	Mike Foley <mfoley>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	JON 3.2	CC:	theute
Target Milestone:	---
Target Release:	JON 4.0.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-06-24 15:06:15 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:
Bug Depends On:
Bug Blocks:	919199

Description Libor Zoubek 2013-03-11 14:07:26 UTC

Description of problem:


Version-Release number of selected component (if applicable):
JON 3.2.0.Alpha + EAP 6.0.GA

How reproducible: Always


Steps to Reproduce:
1. Start 2 instances of EAP6 on same host but different ports
a) Standalone mode on IPv6 : standalone.sh -Djava.net.preferIPv4Stack=false -bmanagement ::1
b) Domain mode on IPv6
2. Import only Domain mode 
3. Create domain deployment on Domain mode EAP
4. Wait for deployment to be discovered by agent
5. Import Standalone EAP
  
Actual results: DomainDeployment created on Domain EAP appears under Standalone EAP as well


Expected results: DomainDeployment resource type should never be child of Standalone server


Additional info:

Comment 1 Libor Zoubek 2013-03-11 15:50:23 UTC

I've just found out, that DomainDeployment created in step 3. is missing on Domain EAP.

Comment 4 Filip Brychta 2019-06-24 15:06:15 UTC

JBoss ON is coming to the end of its product life cycle. For more information regarding this transition, see https://access.redhat.com/articles/3827121.
This bug report/request is being closed. If you feel this issue should not be closed or requires further review, please create a new bug report against the latest supported JBoss ON 3.3 version.