Bug 1261838 - [geo-rep]: Multiple geo-rep session to the same slave is allowed for different users
[geo-rep]: Multiple geo-rep session to the same slave is allowed for differen...
Product: Red Hat Gluster Storage
Classification: Red Hat
Component: geo-replication (Show other bugs)
x86_64 Linux
high Severity high
: ---
: RHGS 3.1.3
Assigned To: Saravanakumar
Rahul Hinduja
: ZStream
Depends On:
Blocks: 1294813 1299184 1335728 1336704
  Show dependency treegraph
Reported: 2015-09-10 05:45 EDT by Rahul Hinduja
Modified: 2016-06-23 00:55 EDT (History)
6 users (show)

See Also:
Fixed In Version: glusterfs-3.7.9-5
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 1294813 (view as bug list)
Last Closed: 2016-06-23 00:55:11 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:1240 normal SHIPPED_LIVE Red Hat Gluster Storage 3.1 Update 3 2016-06-23 04:51:28 EDT

  None (edit)
Description Rahul Hinduja 2015-09-10 05:45:02 EDT
Description of problem:

If the slave volume is part of any geo-rep session, then another attempt to use the same slave volume should be restricted. This is currently allowed if the session is already established as root and another attempt is made using user. 

In this case master volume info file is appended with both the slave entries one with slavehostname and another with <user>@slavehostname.

Now, if any one of the geo-rep session is deleted for example root session. All the session gets deleted.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. Create and start geo-rep session between master and slave {root}
2. Create another geo-rep session between same master ans slave using same slave host but with user account {non-root}

Actual results:

Able to create the session

Expected results:

If slave is part of any geo-rep session the subsequent attempt to create different geo-rep session should fail
Comment 3 Aravinda VK 2016-01-13 02:58:05 EST
Patch sent to Upstream
Comment 5 Mike McCune 2016-03-28 19:32:32 EDT
This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune@redhat.com with any questions
Comment 6 Aravinda VK 2016-05-13 02:35:08 EDT
Downstream patch sent
Comment 8 Rahul Hinduja 2016-05-28 13:26:26 EDT
Verified with the build: 

With the latest changes, existing geo-rep session between master and slave can be converted to secure(non-root) or different users. But at any given point in time, only one session between master and slave can be active and hence the existing geo-rep session needs to be stoped before creating with other user. 

Verified the above scenario, which works. Moving the bug to verified state.
Comment 12 errata-xmlrpc 2016-06-23 00:55:11 EDT
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.


Note You need to log in before you can comment on or make changes to this bug.