diff options
| author | Saravanakumar Arumugam <sarumuga@redhat.com> | 2016-05-30 17:34:24 +0530 |
|---|---|---|
| committer | Aravinda VK <avishwan@redhat.com> | 2016-06-02 03:53:27 -0700 |
| commit | a8d86daf45d4999b885c799307df4ab1abfd25f4 (patch) | |
| tree | bc6bec432dd0b970c318cf7f52def2cbffccb860 /extras/failed-tests.py | |
| parent | 0673af0f0c7ba64cce6b030b9194b4d35a357cd4 (diff) | |
geo-rep: update peers section in gsyncd conf
Problem:
Once Slave volume uuid is involved as part of a geo-rep session, it is
possible to create the same geo-rep session with different (slave)host.
But, it reflects default values for geo-rep configuration values originally
configured for old geo-rep session.
Reason is, slave host is used while saving config options in gsyncd.conf.
With new slave host, it is not possible to retrieve those config values.
Solution:
Remove slave host related information from gsyncd.conf and have only master
volume and slave volume as part of peers section.
Also, during upgrade from old geo-rep session, update peers section to
reflect only master volume and slave volume.
Change-Id: I7debf35a09a28d030b706b0c3e5d82c9b0467d0e
BUG: 1341108
Reviewed-on: http://review.gluster.org/#/c/14558/
Signed-off-by: Saravanakumar Arumugam <sarumuga@redhat.com>
Reviewed-on: http://review.gluster.org/14565
Smoke: Gluster Build System <jenkins@build.gluster.com>
NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
Reviewed-by: Aravinda VK <avishwan@redhat.com>
Diffstat (limited to 'extras/failed-tests.py')
0 files changed, 0 insertions, 0 deletions
