Bug 1517633

Summary:	Geo-rep: access-mount config is not working
Product:	[Community] GlusterFS	Reporter:	Kotresh HR <khiremat>
Component:	geo-replication	Assignee:	Kotresh HR <khiremat>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	mainline	CC:	bugs
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	glusterfs-4.0.0	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-03-15 11:21:35 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:

Description Kotresh HR 2017-11-27 06:42:10 UTC

Description of problem:
access-mount config is not working. By default, the geo-rep mount should not be accessible for the admin. Geo-rep process gets into the mount and do lazy umount so others can't access it. Now, by default the geo-rep mount is accessible even after setting access-mount to false.

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

How reproducible:
Always

Steps to Reproduce:
1. Setup geo-rep between two gluster volumes
2. Check the df output


Actual results:
Geo-rep mount is accessible by default and is not configurable

Expected results:
Geo-rep mount should not be accessible by default and should be configurable

Additional info:

Comment 1 Worker Ant 2017-11-27 07:34:14 UTC

REVIEW: https://review.gluster.org/18858 (geo-rep: Fix access-mount geo-rep config) posted (#1) for review on master by Kotresh HR

Comment 2 Worker Ant 2017-11-30 06:33:23 UTC

COMMIT: https://review.gluster.org/18858 committed in master by \"Kotresh HR\" <khiremat> with a commit message- geo-rep: Fix access-mount geo-rep config

Fix access-mount and slave-access-mount
configs.

Change-Id: Ib586677755e76a51b9f20093e441b72789b4fecc
Signed-off-by: Kotresh HR <khiremat>
BUG: 1517633

Comment 3 Shyamsundar 2018-03-15 11:21:35 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-4.0.0, please open a new bug report.

glusterfs-4.0.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://lists.gluster.org/pipermail/announce/2018-March/000092.html
[2] https://www.gluster.org/pipermail/gluster-users/