Migration issue after replacing a node

ppl:
1. Open the node you want to move vm/ct
2. go to: /etc/ssh/
3. get key from file: ssh_host_rsa_key.pub
4. Go to node from which you want to move vm/ct
5. Open file /etc/ssh/ssh_know_hosts
6. comment (#) line with destination node name
7. Add new line proxmox ssh-rsa AAAAB3NzaCasdfasdf23523gdvfshsdfhzSbX0MVKXsbHXBmsMys8HSz4m9f6ebE6n6d0BIKxHy/hr7dctaHtbO
where 'proxmox' is your node name (the one you want to connect)
 
  • Like
Reactions: PhaseIV and evandromac
RobertMoon said:
ppl:
1. Open the node you want to move vm/ct
2. go to: /etc/ssh/
3. get key from file: ssh_host_rsa_key.pub
4. Go to node from which you want to move vm/ct
5. Open file /etc/ssh/ssh_know_hosts
6. comment (#) line with destination node name
7. Add new line proxmox ssh-rsa AAAAB3NzaCasdfasdf23523gdvfshsdfhzSbX0MVKXsbHXBmsMys8HSz4m9f6ebE6n6d0BIKxHy/hr7dctaHtbO
where 'proxmox' is your node name (the one you want to connect)
Click to expand...
Thank you, my friend. Your solution worked fine for me here.
 
Similar problem and solution
========================================================
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
SHA256:8SH9c9vnuZ1Q0cjPsLAzqBquiWVG0UkhnUA6U5uYgrE.
Please contact your system administrator.
Add correct host key in /root/.ssh/known_hosts to get rid of this message.
Offending RSA key in /etc/ssh/ssh_known_hosts:4
remove with:
ssh-keygen -f "/etc/ssh/ssh_known_hosts" -R "192.168.0.5"
RSA host key for 192.168.0.5 has changed and you have requested strict checking.
Host key verification failed.
========================================================

The problem arose due to the retirement of node2 from a cluster of 3 pieces (pve1, pve2, pve3) there was a problem with node2 (pve2), it was deleted and then reinstalled and connected again, the problem described above arose. The problem arose when connecting in the _Shell web console to a virtual ST (located on node2).
Decision:
1. I went to the console using the ssh of each old node (1,3) ssh (on node2 where the problem is, you don’t need to execute it, there is no erroneous entry).
2. Executed the command ssh-keygen -f "/etc/ssh/ssh_known_hosts" -R "192.168.0.5".
After that, entering the node2 web console and calling "_Shell" node2, I received an invitation to accept the changes.
This fixed the error described above.

Hope this helps someone in the future.
 
You must log in or register to reply here.
Top Bottom