[jboss-jira] [JBoss JIRA] (WFLY-1437) Cannot remove JGroups subsystem from managed domain via CLI

[RH Bugzilla Integration (JIRA)]

    [ https://issues.jboss.org/browse/WFLY-1437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12804661#comment-12804661 ] 

RH Bugzilla Integration commented on WFLY-1437:
-----------------------------------------------

mark yarborough <myarboro at redhat.com> changed the Status of [bug 968815|https://bugzilla.redhat.com/show_bug.cgi?id=968815] from VERIFIED to CLOSED
                
> Cannot remove JGroups subsystem from managed domain via CLI
> -----------------------------------------------------------
>
>                 Key: WFLY-1437
>                 URL: https://issues.jboss.org/browse/WFLY-1437
>             Project: WildFly
>          Issue Type: Bug
>          Components: Clustering, Domain Management
>    Affects Versions: 8.0.0.Alpha1
>            Reporter: Brian Stansberry
>            Assignee: Brian Stansberry
>             Fix For: 8.0.0.Alpha2
>
>
> Osamu Nagano reports:
> "Description of problem:
> In EAP 6.1 domain mode, try to create a new profile from scratch in CLI.  You can add jgroups subsystem but you cannot remove it with an error message.
> In standalone mode and both modes of EAP 6.0.1, you can successfully remove it.
> Steps to Reproduce:
> 1. Start EAP 6.1 in domain mode.  The default domain.xml is sufficient.
> 2. Connect to the DC by CLI.
> 3. Execute the following commands in CLI.
> --
> [domain at localhost:9999 /] /profile=test:add()
> [domain at localhost:9999 /] /profile=test/subsystem=jgroups:add(default-stack=udp)
> [domain at localhost:9999 /] /profile=test/subsystem=jgroups:remove()
> --
> Actual results:
> {
>     "outcome" => "failed",
>     "failure-description" => {"domain-failure-description" => "JBAS014807: Management resource '[(\"subsystem\" => \"jgroups\")]' not found"},
>     "rolled-back" => true
> }
> Expected results:
> {
>     "outcome" => "success",
>     "result" => undefined,
>     "server-groups" => undefined
> }
> "
> I see that the problem exists in WildFly as well.
> The problem is in JGroupsSubsystemRemove:
> ModelNode removeSubsystem = Util.createOperation(REMOVE, PathAddress.pathAddress(JGroupsExtension.SUBSYSTEM_PATH));
>         context.addStep(removeSubsystem, new OriginalSubsystemRemoveHandler(), OperationContext.Stage.MODEL, true);
> That PathAddress.pathAddress(JGroupsExtension.SUBSYSTEM_PATH) is incorrect in a managed domain, as it doesn't include the profile element. It's correct in a standalone server.
> Easy fix.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira