Bug 825562

Summary: [glusterfs-3.3.0q43]: clear-locks attempts to connect using privileged port
Product: [Community] GlusterFS Reporter: Joe Julian <joe>
Component: cliAssignee: krishnan parthasarathi <kparthas>
Status: CLOSED WORKSFORME QA Contact:
Severity: high Docs Contact:
Priority: medium    
Version: pre-releaseCC: amarts, gluster-bugs, nsathyan
Target Milestone: ---Keywords: Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 849291 (view as bug list) Environment:
Last Closed: 2012-12-27 01:11:22 EST Type: Bug
Regression: --- Mount Type: ---
Documentation: DP CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Bug Depends On:    
Bug Blocks: 849291    
Attachments:
Description Flags
mysql1-clearlocks-mnt.log
none
ewcs2:var-spool-glusterfs-a_mysql1.log
none
ewcs2: b,c,d
none
ewcs4: var-spool-glusterfs-{a,b,c,d}_mysql1.log none

Description Joe Julian 2012-05-27 15:57:54 EDT
Version: 3.3.0qa34

clear-locks commands fail if rpc-auth-allow is not set as it attempts to connect via privileged port.

The CLI reports the error as:
Volume clear-locks unsuccessful
clear-locks getxattr command failed. Reason: Transport endpoint is not connected

### glusterd.vol.log has
[2012-05-27 12:54:33.217491] E [rpcsvc.c:491:rpcsvc_handle_rpc_call] 0-glusterd: Request received from non-privileged port. Failing request
Comment 1 Joe Julian 2012-05-28 02:49:01 EDT
Did it again. Sorry, it's qa43 not 34.
Comment 2 Joe Julian 2012-05-28 05:37:31 EDT
Created attachment 587189 [details]
mysql1-clearlocks-mnt.log
Comment 3 Joe Julian 2012-05-28 06:02:06 EDT
Created attachment 587198 [details]
ewcs2:var-spool-glusterfs-a_mysql1.log
Comment 4 Joe Julian 2012-05-28 06:11:43 EDT
Created attachment 587200 [details]
ewcs2: b,c,d
Comment 5 Joe Julian 2012-05-28 06:15:34 EDT
Created attachment 587203 [details]
ewcs4: var-spool-glusterfs-{a,b,c,d}_mysql1.log

Each of these logs are for just the minutes that were in the clearlocks log. Let me know if that's not what you needed.
Comment 6 Amar Tumballi 2012-12-21 04:45:35 EST
one of the work around is to make sure everything works by adding "rpc-auth-allow-insecure yes" in volume files (both glusterd.vol and glusterfsd.vol, for which one can do 'gluster volume set <VOL> server.allow-insecure yes').

as the work around exists, would like to move the priority to medium.
Comment 7 Amar Tumballi 2012-12-27 01:10:15 EST
----------
amar@supernova:~/work/glusterfs$ git diff
diff --git a/doc/glusterd.vol b/doc/glusterd.vol
index de17d8f..8268c3d 100644
--- a/doc/glusterd.vol
+++ b/doc/glusterd.vol
@@ -4,5 +4,12 @@ volume management
     option transport-type socket,rdma
     option transport.socket.keepalive-time 10
     option transport.socket.keepalive-interval 2
+
+  # enable below option only if there are not many ports free below 1024
+  # to bind() the client process. In this case, you would have to run :
+  # 'gluster volume set <VOL> server.allow-insecure yes'
+  # on all the volumes to the proper functioning.
+  #
+#   option rpc-auth-allow-insecure yes
     option transport.socket.read-fail-log off
 end-volume
----------

The above patch is the only way at the moment to fix these things.

Also, Would like to close the bug with D(ocumentation)P(ending) flag set, once we have more better way of handling security (SSL/Kerberos etc), this issue will go away.
Comment 8 Amar Tumballi 2012-12-27 01:11:22 EST
as per comment #7 (WORKSFORME always when we have the above two options set). WONTFIX the part of not having these options set for now.