Description of problem:
When a node is added in Master/Slave, we have to run Geo-rep create push-pem force and Start force to distribute Master public keys to Slave nodes.
This commands adds duplicate entries in authorized_keys file of existing slave nodes.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Create push-pem geo-rep session, check the authorized_keys file in slave nodes.
2. Run Geo-rep create again with force and check the authorized_keys file in slave nodes.
Duplicate entries in authorized_keys file.
Should not be duplicate entries in authorized_keys file in slave nodes.
REVIEW: http://review.gluster.org/9776 (geo-rep: Avoid duplicate entries in authorized_keys file) posted (#1) for review on master by Aravinda VK (email@example.com)
COMMIT: http://review.gluster.org/9776 committed in master by Vijay Bellur (firstname.lastname@example.org)
Author: Aravinda VK <email@example.com>
Date: Sun Mar 1 11:48:12 2015 +0530
geo-rep: Avoid duplicate entries in authorized_keys file
When Georep create(force) command is run multiple times
it appends master nodes public keys to Slave nodes without
checking the existence of the key.
With this patch, create push-pem force adds pub key only if
not available in authorized_keys.
Signed-off-by: Aravinda VK <firstname.lastname@example.org>
Tested-by: Gluster Build System <email@example.com>
Reviewed-by: Kotresh HR <firstname.lastname@example.org>
Reviewed-by: Saravanakumar Arumugam <email@example.com>
Reviewed-by: Vijay Bellur <firstname.lastname@example.org>
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.0, please open a new bug report.
glusterfs-3.7.0 has been announced on the Gluster mailinglists , packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist  and the update infrastructure for your distribution.