Alright,
As this is a problem that does not only affect keepalived, but, all
cluster-like softwares dealing with aliases in any existing interface,
managed or not by systemd, I have tested the same test case in a
pacemaker based cluster, with 3 nodes, having 1 virtual IP + a lighttpd
instance
** Also affects: heartbeat (Ubuntu)
Importance: Undecided
Status: New
** Changed in: heartbeat (Ubuntu Bionic)
Importance: Undecided => Medium
** Changed in: heartbeat (Ubuntu Bionic)
Status: New => Triaged
** Changed in: heartbeat (Ubuntu Disco)
Importance: Undecided =>
Based on comment #12, and other comments from other duplicate cases,
I'll summarize here in a better (and consolidated way) how to reproduce
the issue, how to mitigate it using the dummy workaround, and how to fix
it (with the backports/merge requests). At the end I might provide a PPA
asking for
The aforementioned link shows there's been work towards a fix in
systemd. Can't say if that suggests what can be done to improve
keepalived, but I've tagged this "server-next" to get it on the Ubuntu
SErver Team's high priority list, as per Robie's earlier comment.
** Tags added: server-next
--
It looks like there is some clear and actionable work in keepalived here
(even if as a workaround and the real fix ends up being in systemd), so
I'm marking it as Triaged.
FTR, the Ubuntu Server Team is aware of this as a high level issue and
it is high up in our list of priorities to determine
If I understand the keepalived > 2.0.x behavior referred to by cdmiller
above (see 2019-03-07 comment) that is not the appropriate response to
the problem. Granted, it mitigates the consequences butr doesn't
address the underlying issue. A systemd-source issue should not cause
keepalived failover
6 matches
Mail list logo
