[jboss-jira] [JBoss JIRA] (WFLY-3228) ApplyRemoteMasterDomainHandler should use values sent from DC for root resource

Kabir Khan (JIRA) issues at jboss.org
Mon Apr 7 17:38:13 EDT 2014


     [ https://issues.jboss.org/browse/WFLY-3228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kabir Khan updated WFLY-3228:
-----------------------------

    Description: 
This is needed to keep the slave copy of the resource model actually the same, and popped up during mixed domain testing of EAP with a 6.2.0 slave.

Connect directly to to 6.1.1 slave - gets domain version from master
{code}
[domain at localhost:19999 /] :read-resource
{
    "outcome" => "success",
    "result" => {
        "deployment" => undefined,
        "deployment-overlay" => undefined,
        "management-major-version" => 1,
        "management-micro-version" => 0,
        "management-minor-version" => 6,
        "name" => "Unnamed Domain",
        "namespaces" => [],
        "path" => undefined,
        "product-name" => "EAP",
        "product-version" => "6.3.0.Alpha3",
        "profile" => undefined,
        "release-codename" => "Janus",
        "release-version" => "7.4.0.Final-redhat-SNAPSHOT",
 {code}
Connect directly to 6.2.0 slave - does not get domain version from master
{code}
[domain at localhost:19999 /] :read-resource
{
    "outcome" => "success",
    "result" => {
        "management-major-version" => 1,
        "management-micro-version" => 0,
        "management-minor-version" => 5,
        "name" => "Unnamed Domain",
        "namespaces" => [],
        "product-name" => "EAP",
        "product-version" => "6.2.0.GA",
        "release-codename" => "Janus",
        "release-version" => "7.3.0.Final-redhat-14",
{code}
The 6.2.0 slave should look the same as the 6.1.1 slave for these attributes. 

  was:This is needed to keep the slave copy of the resource model actually the same, and popped up during mixed domain testing of EAP with a 6.2.0 slave.


    
> ApplyRemoteMasterDomainHandler should use values sent from DC for root resource
> -------------------------------------------------------------------------------
>
>                 Key: WFLY-3228
>                 URL: https://issues.jboss.org/browse/WFLY-3228
>             Project: WildFly
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 8.0.0.Final
>            Reporter: Kabir Khan
>            Assignee: Kabir Khan
>             Fix For: 8.0.1.Final
>
>
> This is needed to keep the slave copy of the resource model actually the same, and popped up during mixed domain testing of EAP with a 6.2.0 slave.
> Connect directly to to 6.1.1 slave - gets domain version from master
> {code}
> [domain at localhost:19999 /] :read-resource
> {
>     "outcome" => "success",
>     "result" => {
>         "deployment" => undefined,
>         "deployment-overlay" => undefined,
>         "management-major-version" => 1,
>         "management-micro-version" => 0,
>         "management-minor-version" => 6,
>         "name" => "Unnamed Domain",
>         "namespaces" => [],
>         "path" => undefined,
>         "product-name" => "EAP",
>         "product-version" => "6.3.0.Alpha3",
>         "profile" => undefined,
>         "release-codename" => "Janus",
>         "release-version" => "7.4.0.Final-redhat-SNAPSHOT",
>  {code}
> Connect directly to 6.2.0 slave - does not get domain version from master
> {code}
> [domain at localhost:19999 /] :read-resource
> {
>     "outcome" => "success",
>     "result" => {
>         "management-major-version" => 1,
>         "management-micro-version" => 0,
>         "management-minor-version" => 5,
>         "name" => "Unnamed Domain",
>         "namespaces" => [],
>         "product-name" => "EAP",
>         "product-version" => "6.2.0.GA",
>         "release-codename" => "Janus",
>         "release-version" => "7.3.0.Final-redhat-14",
> {code}
> The 6.2.0 slave should look the same as the 6.1.1 slave for these attributes. 

--
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


More information about the jboss-jira mailing list