[jboss-jira] [JBoss JIRA] (WFCORE-1775) CLI command for enabling tracking configuration changes act differently when host is specifiend and when it is not

[Brian Stansberry (JIRA)]

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

Brian Stansberry commented on WFCORE-1775:
------------------------------------------

This is correct behavior. Connecting to a non-master HC and trying to invoke any write operation for a resource not in the /host=* tree should produce that error. Not producing that error is a bug.

> CLI command for enabling tracking configuration changes act differently when host is specifiend and when it is not
> ------------------------------------------------------------------------------------------------------------------
>
>                 Key: WFCORE-1775
>                 URL: https://issues.jboss.org/browse/WFCORE-1775
>             Project: WildFly Core
>          Issue Type: Bug
>          Components: Domain Management
>            Reporter: Ivan Straka
>            Assignee: Brian Stansberry
>
> If I execute 
> {code}
> /host=slave/core-service=management/service=configuration-changes:add(history-size=10)
> {code}
> on host controller, everything is fine. 
> But, if 
> {code}
> /core-service=management/service=configuration-changes:add(history-size=10) 
> {code}
> is executed,
> {code:json}
> {
>     "outcome" => "failed",
>     "failure-description" => "WFLYDC0032: Operation add for address [
>     (\"core-service\" => \"management\"),
>     (\"service\" => \"configuration-changes\")
> ] can only be handled by the master Domain Controller; this host is not the master Domain Controller",
>     "rolled-back" => true
> }
> {code}
> is returned.
> I have discussed this with [~ehugonnet], and it has not been decided whether this is correct behavior. For some reason it is trying to route the request to the DC.
> This jira is supposed to start a discussion about this - is it a bug, or correct behavior?
> IMHO results of these two commands should should be the same.



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)