D
Deleted member 33567
Guest
Alto I have specifically disabled the external IPS it seems for some reason the migration tries to use external ip over local ips. Note all these. behaviours are only present in latest releases, last 1 month broked also the ceph cluster that might be unrelated or disk issue, i still debug that and opened a separate thread.
The connection should be made towards root@172.17.1.1,2,3 depending on node.
What I found very disturbing is how can it use the exteral ip when in /etc/hosts is disabled:

I have restarted all proxmox services and the n01 got its local ip back.
Code:
2020-10-17 07:41:46 # /usr/bin/ssh -e none -o 'BatchMode=yes' -o 'HostKeyAlias=n01-sxb-pve01' root@51.91.75.99 /bin/true
2020-10-17 07:41:46 ssh: connect to host 51.91.75.99 port 22: Connection refused
2020-10-17 07:41:46 ERROR: migration aborted (duration 00:00:00): Can't connect to destination address using public key
TASK ERROR: migration aborted
The connection should be made towards root@172.17.1.1,2,3 depending on node.
What I found very disturbing is how can it use the exteral ip when in /etc/hosts is disabled:

I have restarted all proxmox services and the n01 got its local ip back.
Last edited by a moderator: