ifupdown is not deprecated. but a lot of new feature are coming for ifupdown2 (vxlan,....).@spirit Thanks for the suggestion!
But as I said, first problem is that it happens occasionally, so I may think everything is ok, but one fine day cluster would not start up.
The second thing that I mentioned, is that ifupdown2 ignores 'post-up' statements on no-subscription cluster.
So.. no trust to ifupdown2 anymore.
Is there any reason to switch to ifupdown2 (except applying changes without reboot)? Is ifupdown deprecated?
Great, thanks for the info!but a lot of new feature are coming for ifupdown2 (vxlan,....).
Sure, I've sent /etc/network/interfaces of all the nodes of that cluster in PM.about the post-up, can you send your /etc/network/interfaces with post-up ?
what is your router model ?Ok, so I'm getting a flood of this same error, and then a Proxmox reboot, on all three of my nodes when I reboot my router?!??
what is your router model ?
This error should mean that a sended packet by your host, is coming back to your host. (so switch is flooding to all port for example, or a network loop).
Maybe it could be a router software bug, when you reboot it. (do you have tried to hard poweroff your router to compare ?)
if it's really a loop, with network amplification, it could overload corosync process. (I have see that once, as corosync only use 1core, it was 100%).
if ha is enabled, it could reboot the hosts.