Bug 1322811

Summary: EAP7 - messaging-activemq subsystem is not discovered in full profile of domain controller
Product: [JBoss] JBoss Operations Network Reporter: Filip Brychta <fbrychta>
Component: Plugin -- JBoss EAP 7Assignee: Michael Burman <miburman>
Status: CLOSED CURRENTRELEASE QA Contact: Filip Brychta <fbrychta>
Severity: high Docs Contact:
Priority: high    
Version: JON 3.3.5CC: loleary, miburman, rhatlapa, spinder
Target Milestone: ER01Keywords: Triaged
Target Release: One-off release   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-06-06 18:58:16 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:
Bug Depends On:    
Bug Blocks: 1314853    

Description Filip Brychta 2016-03-31 11:26:53 UTC 
Description of problem:
EAP7 full profile contains messaging-activemq subsystem but it's not discovered by JON.
From jboss-cli:
[domain.0.1:8990 /] /profile=full/subsystem=messaging-activemq:read-resource
{
    "outcome" => "success",
    "result" => {
        "jms-bridge" => undefined,
        "server" => {"default" => undefined}
    }
}

subsystem is there but it's not discovered by JON.


Version-Release number of selected component (if applicable):
JON 3.3.5 + eap plugin pack update04-DR01

How reproducible:
Always

Steps to Reproduce:
1. import domain EAP 7 Domain controller resource to JON inventory
2. go to profiles->full->subsystems


Actual results:
messaging-activemq subsystem is not there

Expected results:
messaging-activemq subsystem should be there

Additional info:
messaging-activemq subsystem is discovered correctly in eap 7 standalone
Comment 1 Michael Burman 2016-04-04 08:20:22 UTC 
Fixed in the master:

commit da4682f49f73c02fd6f4e03f97e23c8765f07b86
Author: Michael Burman <miburman>
Date:   Mon Apr 4 11:19:42 2016 +0300

    [BZ 1322811] Fix path of ActiveMQMessaging (Profile)