From 5a8dd6f39ec6a536cf13b2758a754947ded16a23 Mon Sep 17 00:00:00 2001 From: M S Vishwanath Bhat Date: Thu, 4 Jun 2015 17:52:00 +0530 Subject: gverify: Adding StrictHostKeyChecking=no for ssh verification Before actually checking the compatibility between master and slave, gverify checks if there is a passwordless ssh connection between master to slave. So if the entry of the slave was not present in 'known_hosts' file in master gverify used to complain that passwordless ssh has not been setup. This used to happen even if there is a passwordless ssh between master to slave. This patch fixes the above problem by using StrictHostKeyChecking=no while doing ssh to slave. Reviewed-on: http://review.gluster.org/11106 Change-Id: I01577ffa82a4504b4674fe26a5256ca890777557 BUG: 1231678 Signed-off-by: M S Vishwanath Bhat Reviewed-on: http://review.gluster.org/11225 Tested-by: NetBSD Build System Tested-by: Gluster Build System Reviewed-by: Aravinda VK --- geo-replication/src/gverify.sh | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'geo-replication/src') diff --git a/geo-replication/src/gverify.sh b/geo-replication/src/gverify.sh index e661267ce50..607be4aeace 100755 --- a/geo-replication/src/gverify.sh +++ b/geo-replication/src/gverify.sh @@ -134,7 +134,7 @@ function main() exit 1; fi; - ssh -oNumberOfPasswordPrompts=0 $2@$3 "echo Testing_Passwordless_SSH"; + ssh -oNumberOfPasswordPrompts=0 -oStrictHostKeyChecking=no $2@$3 "echo Testing_Passwordless_SSH"; if [ $? -ne 0 ]; then echo "FORCE_BLOCKER|Passwordless ssh login has not been setup with $3 for user $2." > $log_file exit 1; -- cgit