Bug 764444 (GLUSTER-2712)

Summary: username resolution in gsyncd fails
Product: [Community] GlusterFS Reporter: Csaba Henk <csaba>
Component: geo-replicationAssignee: Csaba Henk <csaba>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: mainlineCC: gluster-bugs, lakshmipathi
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: ---
Regression: RTA Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Anand Avati 2011-04-11 09:44:16 UTC 
PATCH: http://patches.gluster.com/patch/6789 in master (syncdaemon: do not use os.getlogin() for getting the name of the current user)
Comment 1 Csaba Henk 2011-04-11 11:08:44 UTC 
Commands:

gluster volume gsync start :pop localhost::yow

and

gluster volume gsync start :pop root@localhost::yow

are expected to be equivalent (because, as in ssh, remote username defaults to the actual username). However, the first form fails.
Comment 2 Lakshmipathi G 2011-04-15 11:49:43 UTC 
verified with 3.2.0qa12.