[jboss-jira] [JBoss JIRA] (WFLY-10702) Cover possible error when host controllers can not connect to domain after creating a rollout plan and restarting the master host controller

[Jiri Ondrusek (JIRA)]

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

Jiri Ondrusek updated WFLY-10702:
---------------------------------
    Steps to Reproduce: 
Original problem doesn't happen on wildfly - original problem could be simulated on 6.4.x (<6.4.21):
Create a domain with master and slave, create a rollout plan and restart like this:

rollout-plan add --name=my-plan --content={rollout groupa^groupb}
/host=my-dc:reload

  was:See https://issues.jboss.org/browse/JBEAP-15066 for more details (original problem doesn't happen on wildfly)



> Cover possible error when host controllers can not connect to domain after creating a rollout plan and restarting the master host controller
> --------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: WFLY-10702
>                 URL: https://issues.jboss.org/browse/WFLY-10702
>             Project: WildFly
>          Issue Type: Bug
>            Reporter: Jiri Ondrusek
>            Assignee: Jiri Ondrusek
>
> On downstream (6.4.x) there is an error https://bugzilla.redhat.com/show_bug.cgi?id=1599625 about error during restart of master host with rollout plan. This problem doesn't happen on master, but both fix and test should to be created also for wildfly (to satisfy upstream and prevent similar problems to happen - by introducing a test).
> Original problem:
> Creating a rollout plan and restarting the dc host prevent the other hosts to connect to the master again. The slave hc is unable to connect giving the error JBAS014687: Resource is immutable, the dc shows many errors like:
> JBAS012119:  cancelled task by interrupting thread Thread[Host Controller Service Threads - 117,5,Host Controller Service Threads]



--
This message was sent by Atlassian JIRA
(v7.5.0#75005)