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:
I've just found out, that DomainDeployment created in step 3. is missing on Domain EAP.
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.