Description of problem: With commit 79efbe24070220c069f4ae02541f3c433135818e, slave volume uuid is involved as part of slave volume identification. When a volume is already configured for geo-replication(without above patch), upgrade path should be clearly defined. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. create geo-replication session without above mentioned patch. 2. install glusterfs with above mentioned patch. 3. geo-replication session should continue to work after upgrade. Actual results: Expected results: Additional info:
REVIEW: http://review.gluster.org/14425 (glusterd/geo-rep: upgrade path when slave vol uuid involved) posted (#1) for review on master by Saravanakumar Arumugam (sarumuga)
REVIEW: http://review.gluster.org/14425 (glusterd/geo-rep: upgrade path when slave vol uuid involved) posted (#2) for review on master by Saravanakumar Arumugam (sarumuga)
REVIEW: http://review.gluster.org/14425 (glusterd/geo-rep: upgrade path when slave vol uuid involved) posted (#3) for review on master by Saravanakumar Arumugam (sarumuga)
REVIEW: http://review.gluster.org/14425 (glusterd/geo-rep: upgrade path when slave vol uuid involved) posted (#4) for review on master by Saravanakumar Arumugam (sarumuga)
REVIEW: http://review.gluster.org/14425 (glusterd/geo-rep: upgrade path when slave vol uuid involved) posted (#5) for review on master by Saravanakumar Arumugam (sarumuga)
> Description of problem: > > With commit 79efbe24070220c069f4ae02541f3c433135818e, slave volume uuid is > involved as part of slave volume identification. > Typo in git commit id mentioned here, it should be a9128cda34b1f696b717ba09fa0ac5a929be8969. with heading "glusterd/geo-rep: slave volume uuid to identify a geo-rep session"
REVIEW: http://review.gluster.org/14425 (glusterd/geo-rep: upgrade path when slave vol uuid involved) posted (#6) for review on master by Saravanakumar Arumugam (sarumuga)
REVIEW: http://review.gluster.org/14425 (glusterd/geo-rep: upgrade path when slave vol uuid involved) posted (#7) for review on master by Saravanakumar Arumugam (sarumuga)
REVIEW: http://review.gluster.org/14425 (glusterd/geo-rep: upgrade path when slave vol uuid involved) posted (#8) for review on master by Saravanakumar Arumugam (sarumuga)
REVIEW: http://review.gluster.org/14640 (glusterd/geo-rep: upgrade path when slave vol uuid involved) posted (#1) for review on release-3.8 by Saravanakumar Arumugam (sarumuga)
REVIEW: http://review.gluster.org/14425 (glusterd/geo-rep: upgrade path when slave vol uuid involved) posted (#9) for review on master by Kotresh HR (khiremat)
COMMIT: http://review.gluster.org/14425 committed in master by Aravinda VK (avishwan) ------ commit 124425aef8118116d0bd1daa8269ab2c348b2cb9 Author: Saravanakumar Arumugam <sarumuga> Date: Thu May 19 21:13:04 2016 +0530 glusterd/geo-rep: upgrade path when slave vol uuid involved slave volume uuid is involved in identifying a geo-replication session. This patch addresses upgrade path, where existing geo-rep session is gracefully upgraded to involve slave volume uuid. Change-Id: Ib7ff5109b161592f24fc86fc7e93a407655fab86 BUG: 1337473 Signed-off-by: Saravanakumar Arumugam <sarumuga> Signed-off-by: Kotresh HR <khiremat> Reviewed-on: http://review.gluster.org/14425 NetBSD-regression: NetBSD Build System <jenkins.org> CentOS-regression: Gluster Build System <jenkins.com> Smoke: Gluster Build System <jenkins.com> Reviewed-by: Aravinda VK <avishwan>