Removing a node, ssh pub key left behind, offline migration fails

mailinglists

Active Member
Mar 14, 2012
423
36
28
I destroyed and removed a node (pvecm delnode nodename).
Then I installed a new node, but used the same IP and name.

After doing operations like offline migrate I noticed, that ssh automatic login won't work because:
Code:
2019-06-24 17:06:55 # /usr/bin/ssh -e none -o 'BatchMode=yes' -o 'HostKeyAlias=XXX' root@XXX /bin/true
2019-06-24 17:06:55 @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
2019-06-24 17:06:55 @ WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @
2019-06-24 17:06:55 @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
2019-06-24 17:06:55 IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!
so migration fails also.

I will investigate how to best solve this. I tried by removing the offendig keys on source, accepting new ones, but offline migration still fails.
 

mailinglists

Active Member
Mar 14, 2012
423
36
28
I did investigate.
One has to accept default ssh keys for host and IP, then it works.
I just wonder why node name is used instead of IP.
example ssh@nodename instead of ssh@IPofnode
 

Chris

Proxmox Staff Member
Staff member
Jan 2, 2019
382
39
28
Hi, just for your information. A `pvecm updatecerts` might help in such situations. Further, the fingerprints are checked also for the nodenames, not only the IP, so this should make no difference.
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE and Proxmox Mail Gateway. We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get your own in 60 seconds.

Buy now!