diff options
| author | M S Vishwanath Bhat <vbhat@redhat.com> | 2015-06-04 17:52:00 +0530 |
|---|---|---|
| committer | Vijay Bellur <vbellur@redhat.com> | 2015-06-12 23:28:06 -0700 |
| commit | 6b97f339169dd86a3c3aad9cff9b3da83a40a614 (patch) | |
| tree | ac2a76fa2420df36b57692c7fed2b3492bcf9c58 /geo-replication/src | |
| parent | f42be86a10fcd74436da40153d5d84a54d049d49 (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.
Change-Id: I953c278e411ad6bc1dd1966ea6d895b05f890492
BUG: 1228696
Signed-off-by: M S Vishwanath Bhat <vbhat@redhat.com>
Reviewed-on: http://review.gluster.org/11106
Tested-by: Gluster Build System <jenkins@build.gluster.com>
Reviewed-by: Aravinda VK <avishwan@redhat.com>
Diffstat (limited to 'geo-replication/src')
| -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; |