Description of problem: Geo-replication config commands fail when geo-rep status is in 'Created'. It fails with missing pid-file entry from the config file. Version-Release number of selected component (if applicable): master How reproducible: Always Steps to Reproduce: 1. Create master volume and slave volume 2. Establish geo-rep between them. Do not start. 3. gluster vol geo-rep <mastervol> <slavehost>::<slavevol> config use_meta_volume true Actual results: The config command fails Expected results: The config command should not fail. Additional info:
REVIEW: http://review.gluster.org/16132 (glusterd/geo-rep: Fix geo-rep config issue) posted (#1) for review on master by Kotresh HR (khiremat)
REVIEW: http://review.gluster.org/16132 (glusterd/geo-rep: Fix geo-rep config issue) posted (#2) for review on master by Kotresh HR (khiremat)
COMMIT: http://review.gluster.org/16132 committed in master by Atin Mukherjee (amukherj) ------ commit 734da9d94566dbf37984b88df787569fd5209ee2 Author: Kotresh HR <khiremat> Date: Wed Dec 14 07:03:28 2016 -0500 glusterd/geo-rep: Fix geo-rep config issue Problem: Geo-replication config commands fail when geo-rep status is in 'Created'. Cause: During staging phase of geo-rep config, it checks for the existence of 'monitor.pid' file. But the pid file gets created only on start of geo-rep. Hence it fails. Fix: Do not check for the existence of pid-file during staging for config commands. It is not required. Change-Id: I626d368b249cf0423c7f49b4284465508371f566 BUG: 1404678 Signed-off-by: Kotresh HR <khiremat> Reviewed-on: http://review.gluster.org/16132 Smoke: Gluster Build System <jenkins.org> CentOS-regression: Gluster Build System <jenkins.org> NetBSD-regression: NetBSD Build System <jenkins.org> Reviewed-by: Aravinda VK <avishwan> Reviewed-by: Atin Mukherjee <amukherj>
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.10.0, please open a new bug report. glusterfs-3.10.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/gluster-users/2017-February/030119.html [2] https://www.gluster.org/pipermail/gluster-users/