Description of problem:
geo-rep requires passwordless ssh to be setup between geo-rep master to geo-rep slave. But even if password less ssh is setup but the slave file entry is not entered in the ~/.ssh/known_hosts file, gverify.sh throws error saying "passwordless ssh is not setup"
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Create a passwordless ssh between master and slave nodes, but do not have the entry in ~/.ssh/known_hosts file.
2. Run geo-rep create command.
geo-rep create fails with passwordless ssh not setup.
geo-rep create should succeed
REVIEW: http://review.gluster.org/11106 (gverify: Adding StrictHostKeyChecking=no for ssh verification) posted (#2) for review on master by M S Vishwanath Bhat (firstname.lastname@example.org)
Please clone this bug for mainline, and update http://review.gluster.org/11106 to use the cloned bug.
The new clone should be added to the "depends on" field of this bug.
Once the patch has been merged in the master branch, you can send a backport to release-3.7:
(In reply to Niels de Vos from comment #2)
> Please clone this bug for mainline, and update
> http://review.gluster.org/11106 to use the cloned bug.
Agh, I made a mistake while raising the bug I think. Can I just change the version to mainline instead?
I actually sent patch from master branch.
Does that work? I can clone to release-3.7 branch while cherry-pick'ing the patch.
> The new clone should be added to the "depends on" field of this bug.
> Once the patch has been merged in the master branch, you can send a backport
> to release-3.7:
Fix for this BZ is already present in a GlusterFS release. You can find clone of this BZ, fixed in a GlusterFS release and closed. Hence closing this mainline BZ as well.
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.8.0, please open a new bug report.
glusterfs-3.8.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.