Bug 1347206

Summary:	Old documentation link in log during Geo-rep MISCONFIGURATION
Product:	[Community] GlusterFS	Reporter:	Aravinda VK <avishwan>
Component:	geo-replication	Assignee:	Aravinda VK <avishwan>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	3.7.11	CC:	bugs
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-3.7.13	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1343943	Environment:
Last Closed:	2016-07-19 10:50:11 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:	1343943
Bug Blocks:

Description Aravinda VK 2016-06-16 09:53:02 UTC

+++ This bug was initially created as a clone of Bug #1343943 +++

Description of problem:
Following is logged in Geo-rep logs when Geo-rep setup is not correct,

[2016-05-18 02:18:53.765701] W [syncdutils(/bricks/b1):256:log_raise_exception] <top>: !!!!!!!!!!!!! 
[2016-05-18 02:18:53.765799] W [syncdutils(/bricks/b1):257:log_raise_exception] <top>: !!! getting "No such file or directory" errors is most likely due to MISCONFIGURATION, please consult https://access.redhat.com/site/documentation/en-US/Red_Hat_Storage/2.1/html/Administration_Guide/chap-User_Guide-Geo_Rep-Preparation-Settingup_Environment.html 
[2016-05-18 02:18:53.765701] W [syncdutils(/bricks/b1):256:log_raise_exception] <top>: !!!!!!!!!!!!! 
[2016-06-08 11:32:09.540306] E [resource(/bricks/b1):226:errlog] Popen: command "ssh -oPasswordAuthentication=no -oStrictHostKeyChecking=no -i /var/lib/glusterd/geo-replication/secret.pem -p 22 -oControlMaster=auto -S /tmp/gsyncd-aux-ssh-bc3lL1/8b0e044a3aff9be1443052d3dab4f8e2.sock root@fvm1 /usr/local/libexec/gsyncd --session-owner be79b4c8-5d53-49e0-93c2-ba87ffd00a5c -N --listen --timeout 120 gluster://localhost:gv2" returned with 127, saying:
[2016-06-08 11:32:09.540374] E [resource(/bricks/b1):230:logerr] Popen: ssh> bash: /usr/local/libexec/gsyncd: No such file or directory
[2016-06-08 11:32:09.540601] I [syncdutils(/bricks/b1):220:finalize] <top>: exiting.
[2016-06-08 11:32:09.541364] I [repce(agent):92:service_loop] RepceServer: terminating on reaching EOF.
[2016-06-08 11:32:09.541495] I [syncdutils(agent):220:finalize] <top>: exiting.

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


Document link is old and not appropriate.

--- Additional comment from Vijay Bellur on 2016-06-08 07:38:16 EDT ---

REVIEW: http://review.gluster.org/14673 (geo-rep: Error message cleanup) posted (#1) for review on master by Aravinda VK (avishwan)

--- Additional comment from Vijay Bellur on 2016-06-13 06:47:44 EDT ---

REVIEW: http://review.gluster.org/14673 (geo-rep: Error message cleanup) posted (#2) for review on master by Aravinda VK (avishwan)

--- Additional comment from Vijay Bellur on 2016-06-15 13:29:00 EDT ---

COMMIT: http://review.gluster.org/14673 committed in master by Jeff Darcy (jdarcy) 
------
commit 3b69e25c0f3cf0b958fbd2b8459712ad21239caa
Author: Aravinda VK <avishwan>
Date:   Wed Jun 8 16:56:26 2016 +0530

    geo-rep: Error message cleanup
    
    If ssh returns 127 that means the remote gsyncd path is wrong
    or push-pem failed during create. Existing error message was
    pointing old documentation.
    
    Change-Id: Ifbbb4a604fc0ae0fd5cb2746df6363bf28cde1e9
    BUG: 1343943
    Signed-off-by: Aravinda VK <avishwan>
    Reviewed-on: http://review.gluster.org/14673
    Smoke: Gluster Build System <jenkins.org>
    NetBSD-regression: NetBSD Build System <jenkins.org>
    CentOS-regression: Gluster Build System <jenkins.org>
    Reviewed-by: Milind Changire <mchangir>
    Reviewed-by: Kotresh HR <khiremat>

Comment 1 Vijay Bellur 2016-06-16 09:54:45 UTC

REVIEW: http://review.gluster.org/14740 (geo-rep: Error message cleanup) posted (#1) for review on release-3.7 by Aravinda VK (avishwan)

Comment 2 Vijay Bellur 2016-06-27 16:01:40 UTC

COMMIT: http://review.gluster.org/14740 committed in release-3.7 by Aravinda VK (avishwan) 
------
commit 644a7dc6999b909003d16e602619a92b07f7ec31
Author: Aravinda VK <avishwan>
Date:   Wed Jun 8 16:56:26 2016 +0530

    geo-rep: Error message cleanup
    
    If ssh returns 127 that means the remote gsyncd path is wrong
    or push-pem failed during create. Existing error message was
    pointing old documentation.
    
    Change-Id: Ifbbb4a604fc0ae0fd5cb2746df6363bf28cde1e9
    BUG: 1347206
    Signed-off-by: Aravinda VK <avishwan>
    Reviewed-on: http://review.gluster.org/14673
    (cherry picked from commit 3b69e25c0f3cf0b958fbd2b8459712ad21239caa)
    Reviewed-on: http://review.gluster.org/14740
    Smoke: Gluster Build System <jenkins.org>
    NetBSD-regression: NetBSD Build System <jenkins.org>
    CentOS-regression: Gluster Build System <jenkins.org>
    Reviewed-by: Kotresh HR <khiremat>

Comment 3 Kaushal 2016-07-20 13:55:16 UTC

This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.7.13, please open a new bug report.

glusterfs-3.7.13 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution.

[1] https://www.gluster.org/pipermail/gluster-users/2016-July/027604.html
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user