Bug 1235359

Summary:	[geo-rep]: Mountbroker setup goes to Faulty with ssh 'Permission Denied' Errors
Product:	[Community] GlusterFS	Reporter:	Kotresh HR <khiremat>
Component:	geo-replication	Assignee:	Kotresh HR <khiremat>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	mainline	CC:	bugs, gluster-bugs
Target Milestone:	---	Keywords:	Reopened
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-3.8rc2	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:
Clones:	1235360 (view as bug list)		Environment:
Last Closed:	2016-06-16 13:16:31 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:
Bug Blocks:	1235360

Description Kotresh HR 2015-06-24 15:12:05 UTC

Description of problem:
In Geo-Rep Mount broker setup, workers goes to faulty with ssh 'Permission Denied'
Errors

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

How reproducible:


Steps to Reproduce:
1. Setup master volume and start
2. Setup slave volume and start
3. Follow mountbroker setup documentation and create geo-rep session.
4. Start geo-rep session

Actual results:
Session goes to Faulty

Expected results:
Session should not go to faulty

Additional info:

Comment 1 Kotresh HR 2015-06-24 15:17:57 UTC

Patch Posted:
http://review.gluster.org/#/c/11383/

Comment 2 Anand Avati 2015-06-25 11:48:36 UTC

COMMIT: http://review.gluster.org/11383 committed in master by Venky Shankar (vshankar) 
------
commit f1139ca4f8532c35f5f8024610ddc5a412f970e8
Author: Kotresh HR <khiremat>
Date:   Wed Jun 24 20:00:11 2015 +0530

    geo-rep: Fix ssh issue in geo-rep
    
    In geo-rep mountbroker setup, workers fails with
    'Permission Denied' even though the public keys
    are shared to all the slave nodes. The issue
    is with selinux context not being set for .ssh
    and .ssh/authorizedkeys. Doing restorecon on
    these entries to set default selinux security
    context fixes the issue.
    
    Change-Id: I75e16d22f7a168de6c13b0c7571a7ab75761ae0d
    BUG: 1235359
    Signed-off-by: Kotresh HR <khiremat>
    Reviewed-on: http://review.gluster.org/11383
    Tested-by: NetBSD Build System <jenkins.org>
    Reviewed-by: Aravinda VK <avishwan>
    Reviewed-by: darshan n <dnarayan>
    Reviewed-by: Venky Shankar <vshankar>

Comment 3 Nagaprasad Sathyanarayana 2015-10-25 15:22:27 UTC

Fix for this BZ is already present in a GlusterFS release. You can find clone of this BZ, fixed in a GlusterFS release and closed. Hence closing this mainline BZ as well.

Comment 4 Niels de Vos 2016-06-16 13:16:31 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.8.0, please open a new bug report.

glusterfs-3.8.0 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] http://blog.gluster.org/2016/06/glusterfs-3-8-released/
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user