Bug 1539545

Summary:	gsyncd is running gluster command to get config file path is not required
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:	mainline	CC:	bugs
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-v4.1.0	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	1539701 (view as bug list)		Environment:
Last Closed:	2018-06-20 17:58:44 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:	1539701

Description Aravinda VK 2018-01-29 07:31:15 UTC

Description of problem:

With the enhanced Config management(Issue https://github.com/gluster/glusterfs/issues/73), gsyncd should not run gluster command to get config path when spawned.

Comment 1 Worker Ant 2018-01-29 07:33:45 UTC

REVIEW: https://review.gluster.org/19359 (geo-rep: Remove unused working directory check in gsyncd) posted (#1) for review on master by Aravinda VK

Comment 2 Worker Ant 2018-01-29 13:29:25 UTC

COMMIT: https://review.gluster.org/19359 committed in master by $GERRIT_PATCHSET_UPLOADER with a commit message- geo-rep: Remove unused working directory check in gsyncd

To append the default config file path, gsyncd calls gluster
command to get the workdir path and constructs config file path.
This is not required now since the Config management in Geo-replication
is changed with patch 18257(Issue #73)

BUG: 1539545
Change-Id: Ia7eb39e36ed59ece4de65ea7ec71a0f615e338bb
Signed-off-by: Aravinda VK <avishwan>

Comment 3 Worker Ant 2018-01-29 15:26:55 UTC

COMMIT: https://review.gluster.org/19359 committed in master by "Aravinda VK" <avishwan> with a commit message- geo-rep: Remove unused working directory check in gsyncd

To append the default config file path, gsyncd calls gluster
command to get the workdir path and constructs config file path.
This is not required now since the Config management in Geo-replication
is changed with patch 18257(Issue #73)

BUG: 1539545
Change-Id: Ia7eb39e36ed59ece4de65ea7ec71a0f615e338bb
Signed-off-by: Aravinda VK <avishwan>

Comment 4 Shyamsundar 2018-06-20 17:58:44 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-v4.1.0, please open a new bug report.

glusterfs-v4.1.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-June/000102.html
[2] https://www.gluster.org/pipermail/gluster-users/