[jboss-jira] [JBoss JIRA] (WFCORE-1089) IgnoredResourcesProfileCloneTestCase does not wait for domain stabilization following reload

[Brian Stansberry (JIRA)]

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

Brian Stansberry updated WFCORE-1089:
-------------------------------------
    Summary: IgnoredResourcesProfileCloneTestCase does not wait for domain stabilization following reload  (was: IgnoredResourcesProfileCloneTestCase does not well for domain stabilization following reload)


> IgnoredResourcesProfileCloneTestCase does not wait for domain stabilization following reload
> --------------------------------------------------------------------------------------------
>
>                 Key: WFCORE-1089
>                 URL: https://issues.jboss.org/browse/WFCORE-1089
>             Project: WildFly Core
>          Issue Type: Bug
>          Components: Domain Management, Test Suite
>    Affects Versions: 2.0.0.CR9
>            Reporter: Brian Stansberry
>
> IgnoredResourcesProfileCloneTestCase several times reloads the slave HC without restarting its servers. But it then does not wait for those servers to reconnect before continuing on. This means the servers may not be reattached to the domain when further modifications are made.
> I'm quite certain this is the cause of the failure at http://brontes.lab.eng.brq.redhat.com/viewLog.html?buildId=76866&tab=buildResultsDiv&buildTypeId=WildFlyCore_PullRequest#testNameId6713698291695706313 and the other time that test failed.
> IgnoredResourcesProfileCloneTestCase reloads the slave and then exits. CompositeOperationTestCase follows and immediately adds system-property=composite-op in its @Before method. The other-two server doesn't get this op as it's not reconnected. The test then later fails because the other-two server's state is not as expected.



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