diff options
| author | M S Vishwanath Bhat <vbhat@redhat.com> | 2015-06-04 17:52:00 +0530 |
|---|---|---|
| committer | Venky Shankar <vshankar@redhat.com> | 2015-08-10 22:54:34 -0700 |
| commit | 5a8dd6f39ec6a536cf13b2758a754947ded16a23 (patch) | |
| tree | c8131e4ed840a30366e27cbcf509c4f93e1bcdbe /geo-replication | |
| parent | 426d28fbd85486d35dc52b0789d94f4e76d03e66 (diff) | |
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 <vbhat@redhat.com>
Reviewed-on: http://review.gluster.org/11225
Tested-by: NetBSD Build System <jenkins@build.gluster.org>
Tested-by: Gluster Build System <jenkins@build.gluster.com>
Reviewed-by: Aravinda VK <avishwan@redhat.com>
Diffstat (limited to 'geo-replication')
| -rwxr-xr-x | geo-replication/src/gverify.sh | 2 |
1 files changed, 1 insertions, 1 deletions
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; |