[
https://issues.apache.org/jira/browse/GEODE-3316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Swapnil Bawaskar updated GEODE-3316:
------------------------------------
Fix Version/s: 1.3.0
> Fix the order of rolling members in RollingUpgrade related tests
> ----------------------------------------------------------------
>
> Key: GEODE-3316
> URL: https://issues.apache.org/jira/browse/GEODE-3316
> Project: Geode
> Issue Type: Bug
> Components: tests
> Reporter: nabarun
> Assignee: nabarun
> Fix For: 1.3.0
>
>
> In test classes like RollingUpgrade2DUnit and WANRollingUpgrade, there are
> tests with clusters which have new version servers connected to an older
> version locator.
> These tests should be refactored so that everything starts at an older
> version, then follows the following order of upgrade.
> 1. Locators are rolled first to the current version
> 2. Then the servers are upgraded to current version
> 3. And at last the clients are upgraded.
> Queries/ data verification must done in between these steps to confirm that
> the data integrity is maintained while upgrades are happening
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
