Have the same root cause: the fact that systemd-network messes with secondary IP addresses in NICs managed by systemd.
I'm marking all other cases as a duplicate of LP: #1815101.
TODO here is the following:
- There are mainly 2 "fixes" for this issue:
1) keepalived is able to recognize systemd-networkd changes and change cluster status in order to reconfigure managed NICs (keepalived (> 2.0.x)).
2) systemd-networkd implements a new stanza (KeepConfiguration=) to systemd service unit files in order to fix not only this behavior but all those HA related software that manages secondary IPs and/or aliases to NICs being managed by systemd-networkd.
I think the most appropriate would make sure those 2 features work in Eoan, both, together, and then make sure the SRUs are done to Disco and Bionic. One problem w/ the item (2) is that netplan will also have to support the new "KeepConfiguration=" systemd service file stanza, but, the fix (2) is more appropriate for all other HA related softwares controlling virtual IPs (CTDB, Pacemaker, and so ...).
The following 3 bugs:
https:/ /bugs.launchpad .net/bugs/ 1815101 /bugs.launchpad .net/bugs/ 1819074 /bugs.launchpad .net/bugs/ 1810583
https:/
https:/
Have the same root cause: the fact that systemd-network messes with secondary IP addresses in NICs managed by systemd.
I'm marking all other cases as a duplicate of LP: #1815101.
TODO here is the following:
- There are mainly 2 "fixes" for this issue:
1) keepalived is able to recognize systemd-networkd changes and change cluster status in order to reconfigure managed NICs (keepalived (> 2.0.x)).
2) systemd-networkd implements a new stanza (KeepConfigurat ion=) to systemd service unit files in order to fix not only this behavior but all those HA related software that manages secondary IPs and/or aliases to NICs being managed by systemd-networkd.
I think the most appropriate would make sure those 2 features work in Eoan, both, together, and then make sure the SRUs are done to Disco and Bionic. One problem w/ the item (2) is that netplan will also have to support the new "KeepConfigurat ion=" systemd service file stanza, but, the fix (2) is more appropriate for all other HA related softwares controlling virtual IPs (CTDB, Pacemaker, and so ...).