+++ This bug was initially created as a clone of Bug #1235292 +++ +++ This bug was initially created as a clone of Bug #1235225 +++ Description of problem: ======================= The script "set_geo_rep_pem_keys.sh" which does the distribution of the keys for non-root user to all slave nodes, fails as: [root@georep4 scripts]# /usr/libexec/glusterfs/set_geo_rep_pem_keys.sh redhataccount master slave cp: cannot create regular file `/geo-replication/': Is a directory Source file does not exist in /var/lib/glusterd Command executed successfully. [root@georep4 scripts]# The path in the script should be /var/lib/glusterd Version-Release number of selected component (if applicable): ============================================================= How reproducible: ================= Always --- Additional comment from Anand Avati on 2015-06-24 09:25:57 EDT --- REVIEW: http://review.gluster.org/11381 (geo-rep: Fix glusterd working directory) posted (#1) for review on master by Kotresh HR (khiremat)
REVIEW: http://review.gluster.org/11382 (geo-rep: Fix glusterd working directory) posted (#1) for review on release-3.7 by Kotresh HR (khiremat)
COMMIT: http://review.gluster.org/11382 committed in release-3.7 by Venky Shankar (vshankar) ------ commit bdf54579c5cfcc9feb7dc824a5a58255ae14007b Author: Kotresh HR <khiremat> Date: Wed Jun 24 18:30:18 2015 +0530 geo-rep: Fix glusterd working directory Mountbroker setup in geo-replication requires the script 'set_geo_rep_pem_keys.sh to be run manually out of gluster context. Hence the ${GLUSTERD_WORKDIR} is never set. So getting glusterd working dir using 'gluster system:: getwd'. BUG: 1235297 Reviewed-On: http://review.gluster.org/11381 Change-Id: If708ad4294ee726ba7769b8052a0b3a25f93df2a Signed-off-by: Kotresh HR <khiremat> Reviewed-on: http://review.gluster.org/11382 Tested-by: NetBSD Build System <jenkins.org> Tested-by: Gluster Build System <jenkins.com> Reviewed-by: Saravanakumar Arumugam <sarumuga> Reviewed-by: Venky Shankar <vshankar>
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.7.3, please open a new bug report. glusterfs-3.7.3 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://thread.gmane.org/gmane.comp.file-systems.gluster.devel/12078 [2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user