Thanks Karl. This solution from Chris Aumann seems perfect, and I've
just deployed it onto our HAPROXY pair. Just restarted udev and
networkd, and everything survives as expected now. Much appreciated.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
We had this happen again this morning, causing an outage. Same issue,
apt daily leads to a udev restart, which in turn restarted the network
service and caused VRRP address to be lost on both haproxy nodes. I am
going to try and completely disable the apt daily scheduled job while
this bug
Andreas, in our case this was a one off. The system had been running
for 2 months without any issues, and this sudden network restart due to
a daily update check was not expected. We did a lot of testing
different failover events (disconnecting vNIC, powering off a single
node, stopping
Just to add, we also attempted to work around this by adding a systemd
override to netplan to recycle the keepalived service whenever network
management was restarted. While it corrected the issue, it also created
another problem whereby the system hung on startup after a reboot
waiting endlessly
Hi Karl.
I can confirm this issue also, we encountered it this morning on a 2 node
keepalived cluster consisting of 2 VMWARE ubuntu 18.04.1 VMs. In our case, a
daily update task had restarted UDEV, which in turn restarted systemd-networkd.
When this service restarted, the virtual ip on the
