Bug 1340383
Summary: | [geo-rep]: If the session is renamed, geo-rep configuration are not retained | |||
---|---|---|---|---|
Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | Rahul Hinduja <rhinduja> | |
Component: | geo-replication | Assignee: | Saravanakumar <sarumuga> | |
Status: | CLOSED ERRATA | QA Contact: | Rahul Hinduja <rhinduja> | |
Severity: | urgent | Docs Contact: | ||
Priority: | unspecified | |||
Version: | rhgs-3.1 | CC: | amukherj, avishwan, csaba, rcyriac | |
Target Milestone: | --- | Keywords: | ZStream | |
Target Release: | RHGS 3.1.3 | |||
Hardware: | x86_64 | |||
OS: | Linux | |||
Whiteboard: | ||||
Fixed In Version: | glusterfs-3.7.9-7 | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | ||
Clone Of: | ||||
: | 1340853 (view as bug list) | Environment: | ||
Last Closed: | 2016-06-23 05:24:47 UTC | Type: | Bug | |
Regression: | --- | Mount Type: | --- | |
Documentation: | --- | CRM: | ||
Verified Versions: | Category: | --- | ||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
Cloudforms Team: | --- | Target Upstream Version: | ||
Embargoed: | ||||
Bug Depends On: | ||||
Bug Blocks: | 1311817, 1340853, 1341108, 1341121 |
Description
Rahul Hinduja
2016-05-27 08:52:00 UTC
RCA: In gsyncd.conf, "peers" sections contains old Slave Host details. example: peers gluster%3A%2F%2F127.0.0.1%3Atv1 ssh%3A2F%2Froot%40192.168.122.186%3Agluster%3A%2F%2F127.0.0.1%3Atv2 Where, 192.168.122.186 is old slave host IP address. Once the geo-rep session is renamed, old host details are no longer valid. So, with new host, it is NOT possible to get config details. Solution: Remove old host details from peers section. Use only master volume and slave volume as part of peers section and remove slave host detail. Upstream patch http://review.gluster.org/14558 up for review. Downstream patch: https://code.engineering.redhat.com/gerrit/#/c/75488/ Verified with build: glusterfs-3.7.9-7 . Configurations are retained if the existing geo-rep session is renamed. Moving this bug to verified state. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2016:1240 |