Bug#860151: keepalived: System loses virtual ip address after each systemd-networkd restart

2020-06-26 Thread Sam Morris
Package: keepalived Followup-For: Bug #860151 I think this is no longer an issue since systemd 243, which adds the KeepConfiguration= network option. If set to 'yes' then networkd won't remove VIPS and such from managed interfaces when it (re)starts. -- System Information: Debian Release: 10.4

Bug#860151: keepalived: System loses virtual ip address after each systemd-networkd restart

2017-04-12 Thread Vladimir Tiukhtin
I am using same configuration on centos 7.3 and there keepalived detects changes on an interface and reload VIP. That's why I opened it in keepalived - it doesn't detect changes and not reload VRRP instance 2017-04-12 9:26 GMT+01:00 Alexander Wirt : > On Wed, 12 Apr 2017,

Bug#860151: keepalived: System loses virtual ip address after each systemd-networkd restart

2017-04-12 Thread Alexander Wirt
On Wed, 12 Apr 2017, Vladimir Tiukhtin wrote: > Package: keepalived > Version: 1:1.3.2-1 > Severity: normal > > Dear Maintainer, > >* What led up to the situation? > Using systemd-networkd with keepalived I don't think we (Debian) already support systemd-networkd and if systemd-networkd

Bug#860151: keepalived: System loses virtual ip address after each systemd-networkd restart

2017-04-12 Thread Vladimir Tiukhtin
Package: keepalived Version: 1:1.3.2-1 Severity: normal Dear Maintainer, * What led up to the situation? Using systemd-networkd with keepalived * What exactly did you do (or not do) that was effective (or ineffective)? Start systemd-networkd. Start keepalived. Check VIP is applyed.