rpherrera
commented
9 years ago It is possible that you forgot data inside the AMI that you are using to generate others. In case, check out the ".ssh" directory from the same user you are trying to connect to.
It happens from time to time on long running clusters.
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@ WARNING: POSSIBLE DNS SPOOFING DETECTED! @
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
The RSA host key for node005 has changed,
and the key for the corresponding IP address 10.58.54.31
is unknown. This could either mean that
DNS SPOOFING is happening or the IP address for the host
and its host key have changed at the same time.
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@ WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!
Someone could be eavesdropping on you right now (man-in-the-middle attack)! It is also possible that a host key has just been changed.
The fingerprint for the RSA key sent by the remote host is
00:48:68:4c:00:e6:d9:1e:2e:6e:e0:1a:cc:42:90:ff.
Please contact your system administrator.
Add correct host key in /root/.ssh/known_hosts to get rid of this message.
Offending RSA key in /root/.ssh/known_hosts:152
remove with: ssh-keygen -f "/root/.ssh/known_hosts" -R node005
RSA host key for node005 has changed and you have requested strict checking. Host key verification failed.