Hi guys,
i've replaced one of my servers in my cluster - node1 - with a better physical machine, reused the IP and cabling but given it a new name (i have done this before with no issues) - no error messages when adding it to the cluster - but now after trying to migrate a VM to it, its now complaining about an RSA key:
any suggestions on what to do?
i've replaced one of my servers in my cluster - node1 - with a better physical machine, reused the IP and cabling but given it a new name (i have done this before with no issues) - no error messages when adding it to the cluster - but now after trying to migrate a VM to it, its now complaining about an RSA key:
Code:
May 30 11:14:02 # /usr/bin/ssh -c blowfish -o 'BatchMode=yes' root@192.168.15.31 /bin/true
May 30 11:14:02 @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
May 30 11:14:02 @ WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @
May 30 11:14:02 @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
May 30 11:14:02 IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!
May 30 11:14:02 Someone could be eavesdropping on you right now (man-in-the-middle attack)!
May 30 11:14:02 It is also possible that the RSA host key has just been changed.
May 30 11:14:02 The fingerprint for the RSA key sent by the remote host is
May 30 11:14:02 ae:ac:17:56:01:7f:5f:fc:db:34:b4:4e:f5:75:e6:b9.
May 30 11:14:02 Please contact your system administrator.
May 30 11:14:02 Add correct host key in /root/.ssh/known_hosts to get rid of this message.
May 30 11:14:02 Offending key in /root/.ssh/known_hosts:1
May 30 11:14:02 RSA host key for 192.168.15.31 has changed and you have requested strict checking.
May 30 11:14:02 Host key verification failed.
May 30 11:14:02 ERROR: migration aborted (duration 00:00:00): Can't connect to destination address using public key
TASK ERROR: migration aborted