[Bug 1820281] Re: Restarting systemd-networkd breaks keepalived clusters

[sascha arthur]

*** This bug is a duplicate of bug 1815101 ***
    https://bugs.launchpad.net/bugs/1815101

Heres a possible workaround until its solved (did not test it, but seems
valid): https://chr4.org/blog/2019/01/21/make-keepalived-play-nicely-
with-netplan-slash-systemd-network/

Personally i can live with 1-2 sek downtime (on network change), thats
why i added a subscribe hook in puppet to restart keepalived.

Will get rid of the workaround as soon as its solved, which is currently
hardly worked on it seems.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1820281

Title:
  Restarting systemd-networkd breaks keepalived clusters

Status in keepalived package in Ubuntu:
  New
Status in netplan.io package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  Managing a HA floating IP with netplan and keepalived brings trouble.
  Im managing a two node keepalived cluster with a floating IP. 
  Everything works out except if i run on a the master node (which holds floating ip) "netplan apply".
  Prob netplan resets the whole interface, leaving keepalived in a broken state.
  This works without any trouble using the old iproute2 approach.

  Even setting, net.ipv4.conf.*.promote_secondaries does not help out.

  We need definitly an non strict reset option for interfaces in thise
  case.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/keepalived/+bug/1820281/+subscriptions