[Bugs] [Bug 1547446] New: Pause/ Resume of geo-replication with wrong user specified returns success

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1547446

            Bug ID: 1547446
           Summary: Pause/Resume of geo-replication with wrong user
                    specified returns success
           Product: GlusterFS
           Version: 3.12
         Component: geo-replication
          Severity: high
          Assignee: bugs at gluster.org
          Reporter: marcus.pedersen at slu.se
                CC: bugs at gluster.org



Description of problem:
Geo-replication setup with other user then root on slave node,
as described in documentation:
http://docs.gluster.org/en/latest/Administrator%20Guide/Geo%20Replication/
If you run pause or resume on geo-replication with wrong user,
other user then you setup, you will get pause/resume success even
if it does not work.
To make it work again you need to restart glusterd on all nodes.

Version-Release number of selected component (if applicable):
glusterfs 3.12.5 (all packages)

How reproducible:
If geo-replication is setup with user geoaccount, run:
gluster volume geo-replication [volume_name]
anotheruser@[main_slave_node]::[volume_name] pause
Returns:
Pausing geo-replication session between [volume_name] &
anotheruser at main_slave_node]::[volume_name] has been successful
If you create a snapshot you will get the error that you need to stop
geo-replication first.
So geo-replication does not pause

Steps to Reproduce:
1. gluster volume geo-replication [volume_name]
anotheruser@[main_slave_node]::[volume_name] pause
2. gluster snapshot create [snap_name] [volume_name]

Actual results:
Geo-replication returns success with exit code 0 even if wrong user or no user
(root) is specified at pause/resume when geo-replication user is setup.


Expected results:
Return code != 0 and an error message saying that wrong user is specified

Additional info:
Have not tested with root user for geo-replication and specifying another user
at pause/resume

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.