Bug 1104659 - Rest rolling upgrades -- distributed -- new cluster can't load from old cluster properly
Summary: Rest rolling upgrades -- distributed -- new cluster can't load from old clust...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: JBoss Data Grid 6
Classification: JBoss
Component: Server
Version: 6.3.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: 6.3.0
Assignee: Tristan Tarrant
QA Contact: Martin Gencur
URL:
Whiteboard:
: 1104657 1104658 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-06-04 12:57 UTC by Tomas Sykora
Modified: 2014-09-09 07:37 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-07-10 11:52:32 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker ISPN-4343 0 Critical Resolved Rest rolling upgrades, distributed -- new cluster can't load from old cluster properly 2017-05-05 08:22:12 UTC

Description Tomas Sykora 2014-06-04 12:57:54 UTC 
Linked JIRA provides the best overview of the whole issue and also contains a reproducer.
Comment 2 Tomas Sykora 2014-06-05 10:42:53 UTC 
*** Bug 1104657 has been marked as a duplicate of this bug. ***
Comment 3 Tomas Sykora 2014-06-05 10:43:40 UTC 
*** Bug 1104658 has been marked as a duplicate of this bug. ***
Comment 4 Martin Gencur 2014-07-08 07:16:10 UTC 
This need to be documented as a known issue.
Comment 5 JBoss JIRA Server 2014-07-10 11:51:28 UTC 
Tomas Sykora <tsykora> updated the status of jira ISPN-4343 to Resolved
Comment 6 Tomas Sykora 2014-07-10 11:52:32 UTC 
This is not a bug. Closing.
Comment 7 Tomas Sykora 2014-07-10 11:57:47 UTC 
I was able to successfully proceed REST rolling upgrades from 6.2.1.GA to 6.3.0.CR3! 

Tests are using REST helper. There is NO compatibility mode or CLI used; which may cause problems (other BZs reflects that).

This "REST-pure" use case is just working fine.
Note You need to log in before you can comment on or make changes to this bug.