** Summary changed:
- netplan, keepalived, netplan-apply
+ Restarting systemd-networkd breaks keepalived clusters
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
** Also affects: keepalived (Ubuntu)
Importance: Undecided
Status: New
** Changed in: systemd (Ubuntu)
Importance: Undecided => High
** Changed in: netplan.io (Ubuntu)
Importance: Undecided => High
** Changed in: netplan.io (Ubuntu)
Status: New => Confirmed
** Changed in: systemd (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
High Availability Team, which is subscribed to keepalived 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
_______________________________________________
Mailing list: https://launchpad.net/~ubuntu-ha
Post to : ubuntu-ha@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-ha
More help : https://help.launchpad.net/ListHelp
