andy/glusterfs
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

gverify: Adding StrictHostKeyChecking=no for ssh verification

Browse Source 
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>
This commit is contained in:
M S Vishwanath Bhat 2015-06-04 17:52:00 +05:30 committed by Vijay Bellur
parent f42be86a10
commit 6b97f33916
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
geo-replication/src/gverify.sh
View File

@ -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;