SDN broken after setting Vnet tags to 1 and 2

Z

ZZer00

Member
Dec 11, 2021
6
0
6
51
I created 2 new Vnets and without thinking it through set the tags to 1 and 2.
Applied the config and lost connectivity to the box.

I have since gone back in and regained connectivity, but the SDN configuration on that node is now stuck at pending and "local sdn configuration is too old, please reload".
Reloading doesn't work, and rebooting doesn't change anything.

Config files in /etc/pve/sdn/ are the same on both nodes
 
OK, I managed to fix it, so I'll leave this here for anyone else.

For some reason ssh from node 1 to node 2 was broken
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@ WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@

I have no idea how that happended, but it definitely broke the SDN sync.
I reset the certs on both nodes and things are working again

Code: 
pvecm updatecerts -F

systemctl restart pvedaemon pveproxy
 
ZZer00 said:
OK, I managed to fix it, so I'll leave this here for anyone else.

For some reason ssh from node 1 to node 2 was broken
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@ WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@

I have no idea how that happended, but it definitely broke the SDN sync.
I reset the certs on both nodes and things are working again

Code: 
pvecm updatecerts -F

systemctl restart pvedaemon pveproxy
Click to expand...

Could be related to: https://forum.proxmox.com/threads/cannot-migrate-vm-ct-due-to-ssh-key-error.133560/#post-614183
 
You must log in or register to reply here.
Top Bottom