Please re-subscribe the ubuntu-sponsors team to the bug report once the
above has been done.
--
You received this bug notification because you are a member of Ubuntu
High Availability Team, which is subscribed to cluster-agents in Ubuntu.
https://bugs.launchpad.net/bugs/980180
Title:
Apache
Aforementioned patch was included in 2018-04-09 Release 1.4.3
1:1.2.2-3ubuntu1 | precise
1:1.2.2-3ubuntu1.1| precise-updates
1:1.2.7-1ubuntu1 | trusty
1:1.2.13-1~ubuntu14.04.1 | trusty-backports
1:1.2.19-1| xenial
** Patch added:
"0001-Fix-vrrp_script-and-check_misc-scripts-of-type-dev-t.patch"
https://bugs.launchpad.net/ubuntu/+source/keepalived/+bug/1795420/+attachment/5268987/+files/0001-Fix-vrrp_script-and-check_misc-scripts-of-type-dev-t.patch
--
You received this bug notification because you
** Bug watch added: github.com/acassen/keepalived/issues #1112
https://github.com/acassen/keepalived/issues/1112
** Also affects: keepalived via
https://github.com/acassen/keepalived/issues/1112
Importance: Unknown
Status: Unknown
--
You received this bug notification because
Given SRU and backport team policies, having a newer version of
keepalived in bionic seems pretty unlikely. SRU policy favors backports
of specific fixes rather than entire package backports, while the
backports team generally discourages backports of libraries or services
since they can randomly
Oh, one other thing that will be necessary to file an SRU for this would
be a a series of "paint by number" steps to reproduce the issue, and to
verify the fix. For example, something akin to:
https://bugs.launchpad.net/ubuntu/+source/keepalived/+bug/1810583/comments/12
** Also affects:
** Changed in: keepalived (Ubuntu Bionic)
Status: New => Triaged
** Changed in: keepalived (Ubuntu Cosmic)
Status: New => Triaged
** Changed in: keepalived (Ubuntu)
Importance: Undecided => Medium
** Changed in: keepalived (Ubuntu Bionic)
Importance: Undecided => Medium
**
** Tags added: server-next
--
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/1819074
Title:
Keepalived < 2.0.x in Ubuntu 18.04 LTS not compatible with systemd-
in universe at:
https://launchpad.net/ubuntu/+source/heartbeat
** Changed in: heartbeat (Ubuntu)
Status: New => Fix Released
** Changed in: heartbeat (Ubuntu)
Assignee: (unassigned) => Bryce Harrington (bryce)
--
You received this bug notification because you are a member of
** Description changed:
heartbeat was updated to python3[0], but has become obsolescent and can
be removed from the archive.
Release: heartbeat should be removed from main in Eoan+. It can be moved
to universe.
Rationale: Heartbeat was a part of the linux-ha project, and
Public bug reported:
heartbeat was updated to python3[0],but has become obsolescent and can
be removed from the archive.
Release: heartbeat should be removed from main in Eoan+. It can be moved
to universe.
Rationale: Heartbeat was a part of the linux-ha project, and could
** Also affects: pacemaker (Ubuntu Eoan)
Importance: Undecided
Status: Incomplete
** Also affects: pacemaker (Ubuntu Disco)
Importance: Undecided
Status: New
** Changed in: pacemaker (Ubuntu Disco)
Status: New => Confirmed
--
You received this bug notification
pacemaker 2.0 (and its dependencies) will first need merged into Eoan.
I've added a separate task for that from the Disco backport task.
Regarding backporting pacemaker 2.0 to Disco via SRU, the amount of
change from pacemaker 1.1.18 to 2.0.1 is not insignificant, and includes
not only new
** Merge proposal linked:
https://code.launchpad.net/~bryce/ubuntu-seeds/+git/ubuntu-seeds/+merge/366933
--
You received this bug notification because you are a member of Ubuntu
High Availability Team, which is subscribed to heartbeat in Ubuntu.
https://bugs.launchpad.net/bugs/1827416
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
--
Thanks updating status to closed as per last comment. This does sound
like it may be more of a pacemaker issue than haproxy, particularly if
it's still reproducible on a newer LTS.
** Description changed:
`/etc/init.d/haproxy status` will return 0 if the pidfile is present,
regardless of
Cosmic is out of service, so canceling that task. The bug is otherwise
still valid for sru for xenial/bionic if/when someone has time to
package it and finish the SRU form. Meanwhile, if anyone is interested
in helping push this issue towards a fix, the SRU process is documented
at
Thanks for the fix Benoît.
The upstream fix is attached, it's a one line yaml fix to openstack-
ansible's keepalived configuration. The fix looks straightforward
enough, though this bug will need a test case described to reproduce the
fault, esp. if this needs sru'd to bionic or other stable
There's probably a few ways to do the user/group add. Here's one
typical approach.
** Attachment added: "keepalived.postinst"
https://bugs.launchpad.net/ubuntu/+source/keepalived/+bug/1806004/+attachment/5308276/+files/keepalived.postinst
--
You received this bug notification because you
Ah looks like Ubuntu does not package openstack-ansible, so the patch is
not relevant here.
Regarding the keepalived configuration defaults, I see this is hardcoded
at line 983 of lib/notify.c to "keepalived_script"; as you mentioned, it
indeed doesn't appear to be doing a check that the user
Debian should be consulted about this issue, to see if they have
particular druthers regarding the addition of the user, or if they'd
prefer to see this issue fixed some other way (or left as-is for users
to configure themselves). That way we can continue to avoid having a
ubuntu delta for this
...and corresponding postrm
** Attachment added: "keepalived.postrm"
https://bugs.launchpad.net/ubuntu/+source/keepalived/+bug/1806004/+attachment/5308277/+files/keepalived.postrm
--
You received this bug notification because you are a member of Ubuntu
High Availability Team, which is
22 matches
Mail list logo
