Rebuilding Node

thinkdez

Member
Aug 16, 2023
7
1
8
I have a 4 node cluster and one of my nodes died. I had to re-install the OS and rejoin to the cluster. Everything seemed to be working until I went to test out SSH between the nodes. Unfortunately I get the following error message:

Code:
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@    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 ED25519 key sent by the remote host is

Now I have had this before and the fix was to remove the old key from known_hosts. Run pvecm updatecerts -f and all was right with the world. However I seem to be at a loss here. First of my /etc/pve/pric/known_hosts is empty. My /root/.ssh/known_hosts doesn't have the same format as I would expect and I still generate the error message when attempting to ssh to the rebuilt node.

I am running Proxmox VE 9.2.21. I followed the directions in the documentation but I cannot seem to resolve the issue.

I seem to be stuck Any Idea on how I can rebuild my cluster properly? Why are my /etc/pve/priv/known_hosts files blank on all the nodes?
 
Clusters don't like it when old members are rejoined, especially when they are not the actual old members. The approach with clusters is to terminate old/broken/missing members and add new ones. Don't reuse names and IP addresses as that causes issues with private keys like you experienced (using same name and/or same IP but different identify/private key).
 
Last edited:
Clusters don't like it when old members are rejoined, especially when they are not the actual old members. The approach with clusters is to terminate old/broken/missing members and add new ones. Don't reuse names and IP addresses as that causes issues with private keys like you experienced (using same name and/or same IP but different identify/private key).
I get what you are saying but there should be a way to clear the old SSH key. I followed the documentation and removed the old node from the cluster and then I joined the fresh install to the cluster. I kept the same hostname. Am I just supposed to abandon the previous IP space I had forever? Doesn't seem right. I should be able to add a new host with the same IP/name provided I clear out the old configuration as the documentation states. I just feel like the documentation is missing something as I cannot clear the SSH key from the config.