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