ERROR: migration aborted: Can't connect to destination address using public key

K

kalleyne

Renowned Member
May 22, 2013
21
0
66
Good day.

We are using Proxmox VE 2.3 in a cluster with 12 nodes. Generally, VM migrations seem to work but we are having a problem migrating VMs from node 10 to other nodes like node 11 (10.199.0.111).

Jun 06 19:46:11 # /usr/bin/ssh -o 'BatchMode=yes' root@10.199.0.111 /bin/true
Jun 06 19:46:11 Host key verification failed.
Jun 06 19:46:11 ERROR: migration aborted (duration 00:00:00): Can't connect to destination address using public key
TASK ERROR: migration aborted

I had to use the following commands on node 10 a couple days ago because "pvecm add 10.199.0.101" would fail with "unable to create directory '/etc/pve/priv' - file exists":
pvecm updatecerts
/etc/init.d/apache2 restart

This seemed to fix things where apache would start on boot up without errors.

Now, I'm not sure why migrations are failing. Any ideas on how I should proceed?

Thanks.
 
Yes, ssh to 10.199.0.111 works just fine.

Any additional steps that I should take?

Thanks much.
 
More details: There was some light interaction when I made the initial ssh connection from node 10 to 11:

root@proxmox10:~# ssh 10.199.0.111
The authenticity of host '10.199.0.111 (10.199.0.111)' can't be established.
RSA key fingerprint is 10:88:62:e7:59:4a:f8:2b:dd:68:b2:e0:ac:70:e3:d9.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added '10.199.0.111' (RSA) to the list of known hosts.

Repeated attempts to ssh from node 10 to 11 now works flawlessly,
 
Very good.

We retested VM migration from node 10 to 11. Works correctly now.
Thanks for the assistance.
 
You must log in or register to reply here.
Top Bottom