faq WARNING REMOTE HOST IDENTIFICATION HAS CHANGED - padogrid/padogrid GitHub Wiki

When I start a PadoGrid Vagrant VM based cluster, I get "WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED!".

I'm getting the following warning message.

@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@    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 ECDSA key sent by the remote host is
SHA256:uY6GIjFdI9qTC4QYb980QRk+WblJF9cd5glr3SmmL+w.
Please contact your system administrator.
Add correct host key in /Users/dpark/.ssh/known_hosts to get rid of this message.
Offending ECDSA key in /Users/dpark/.ssh/known_hosts:40
ECDSA host key for pnode.local has changed and you have requested strict checking.
Host key verification failed.

This is due to the conflicting public keys in the ~/.ssh/known_hosts file. Edit this file and remove all occurances of the host names (nodes) that match VMs. In our example, they are pnode.local, node-01.local, and node-02.local.

When you create a new PadoGrid Vagrant pod, new keys are created for its VMs. If you have previously created a pod with the same VM host names, then you will see the warning message when you try to start the cluster. To prevent this, you can specify unique host names when you create a pod or remove the key entries in the ~/.ssh/known_hosts file after you created a pod.