Hi Seyeong,
the LP build farm is still unavailable, but once it's back up I'll
review and sponsor this.
--
You received this bug notification because you are a member of Ubuntu
High Availability Team, which is subscribed to pacemaker in Ubuntu.
https://bugs.launchpad.net/bugs/1316970
Title:
** Tags added: sts-sponsor-ddstreet
--
You received this bug notification because you are a member of Ubuntu
High Availability Team, which is subscribed to pacemaker in Ubuntu.
https://bugs.launchpad.net/bugs/1316970
Title:
g_dbus memory leak in lrmd
Status in pacemaker package in Ubuntu:
** Also affects: pacemaker (Ubuntu Trusty)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
High Availability Team, which is subscribed to pacemaker in Ubuntu.
https://bugs.launchpad.net/bugs/1316970
Title:
g_dbus memory leak
Sure, I'll unsubscribe sts-sponsors while you update the patch, just re-
subscribe us when it's ready for review. Thanks!
--
You received this bug notification because you are a member of Ubuntu
High Availability Team, which is subscribed to pacemaker in Ubuntu.
Seyeong,
I prepared a package with the debdiff for uploading, but it is failing
to build during the autopkgtests; can you check that and update the
debdiff please?
configure: creating ./config.status
config.status: creating Makefile
config.status: creating Doxyfile
config.status: creating
Hi Seyeong,
first, I commend you for going to the trouble of fixing tests in
lp1316970_trusty_glib2.0.debdiff, but I think those are unrelated to
this actual bug and so the patch is not required for this. I'll focus
only on the first patch.
In that patch, I did a quick review of the changes,
Seyeong, can you also clarify - are the glib2.0 patches also needed to
fix memory leaks?
--
You received this bug notification because you are a member of Ubuntu
High Availability Team, which is subscribed to pacemaker in Ubuntu.
https://bugs.launchpad.net/bugs/1316970
Title:
g_dbus memory
glib2.0 memleak patch moved over to bug 1750741
** No longer affects: glib2.0 (Ubuntu)
** No longer affects: glib2.0 (Ubuntu Trusty)
--
You received this bug notification because you are a member of Ubuntu
High Availability Team, which is subscribed to pacemaker in Ubuntu.
Ok, in that case, can you open a separate lp bug for the glib2.0 memory
leak? I think it will be easier to track just fixing the pacemaker mem
leaks in this bug, and track fixing the glib2.0 mem leak in a separate
bug.
--
You received this bug notification because you are a member of Ubuntu
sponsored to trusty and xenial
--
You received this bug notification because you are a member of Ubuntu
High Availability Team, which is subscribed to corosync in Ubuntu.
https://bugs.launchpad.net/bugs/1739033
Title:
Corosync: Assertion 'sender_node != NULL' failed when bind iface is
ready
** Description changed:
- [Description]
+ [Impact]
Corosync sigaborts if it starts before the interface it has to bind to
is ready.
On boot, if no interface in the bindnetaddr range is up/configured,
corosync binds to lo (127.0.0.1). Once an applicable interface is up,
corosync
** Changed in: corosync (Ubuntu Xenial)
Status: Incomplete => In Progress
--
You received this bug notification because you are a member of Ubuntu
High Availability Team, which is subscribed to corosync in Ubuntu.
https://bugs.launchpad.net/bugs/1739033
Title:
Corosync: Assertion
** Tags added: sts-sponsor-ddstreet
--
You received this bug notification because you are a member of Ubuntu
High Availability Team, which is subscribed to pacemaker in Ubuntu.
https://bugs.launchpad.net/bugs/1819046
Title:
Systemd unit file reads settings from wrong path
Status in pacemaker
** Tags removed: sts-sponsor sts-sponsor-ddstreet
--
You received this bug notification because you are a member of Ubuntu
High Availability Team, which is subscribed to pacemaker in Ubuntu.
https://bugs.launchpad.net/bugs/1819046
Title:
Systemd unit file reads settings from wrong path
** Tags removed: sts-sponsor
--
You received this bug notification because you are a member of Ubuntu
High Availability Team, which is subscribed to corosync in Ubuntu.
https://bugs.launchpad.net/bugs/1677684
Title:
/usr/bin/corosync-blackbox: 34: /usr/bin/corosync-blackbox: qb-
blackbox:
> So this is wontfix for corosync in disco.
if you say so.
I subscribed the security team since if they ever need to provide a
security release for corosync in disco, this may be the problem they
encounter (and of course, anyone trying to do any normal bugfix to
corosync in disco will also have
Public bug reported:
[impact]
running autopkgtest for corosync in disco with any trigger (e.g. using
--apt-pocket=proposed=src:systemd) fails because the testbed can't find
the corosync source.
[test case]
$ autopkgtest --apt-pocket=proposed=src:systemd --apt-upgrade corosync
-- qemu
or see
There were 3 'corosync' builds that were version 3 in disco-proposed, but none
ever made it out of -proposed:
https://launchpad.net/ubuntu/disco/+source/corosync
There were more builds for corosync-qdevice, and unfortunately those did make
it into disco-release:
see also related pacemaker/pcs bug 1826045
--
You received this bug notification because you are a member of Ubuntu
High Availability Team, which is subscribed to corosync in Ubuntu.
https://bugs.launchpad.net/bugs/1831492
Title:
autopkgtest --apt-pocket=proposed= fails with corosync in
** Description changed:
+ [impact]
+
+ ip addresses managed by keepalived are lost across networkd restarts
+
+ [test case]
+
+ see original description below
+
+ [regression potential]
+
+ this backports KeepConfiguration parameter, which adds some significant
+ complexity to networkd's
as disco reaches EOL next week, marking this as wontfix for disco.
** Changed in: systemd (Ubuntu Disco)
Status: Confirmed => Won't Fix
** Changed in: keepalived (Ubuntu Disco)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
.
** Also affects: pacemaker (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: pacemaker (Ubuntu Xenial)
Status: New => In Progress
** Changed in: pacemaker (Ubuntu Xenial)
Assignee: (unassigned) => Dan Streetman (ddstreet)
** Changed in: pacemaker (Ubuntu
** Description changed:
[impact]
lrmd crashes and dumps core.
[test case]
I can not reproduce, but it is reproducable in the specific setup of the
person reporting the bug to me.
[regression potential]
this patches the cancel/cleanup part of the code, so regressions
Public bug reported:
[impact]
lrmd crashes and dumps core.
[test case]
I can not reproduce, but it is reproducable in the specific setup of the
person reporting the bug to me.
[regression potential]
TBD
[scope]
TBD
[other info]
As mentioned in the test case section, I do not have a setup
** Tags added: ddstreet
--
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/1815101
Title:
[master] Restarting systemd-networkd breaks keepalived, heartbeat,
corosync,
Status update - still waiting on original reporter to perform testing
with -proposed package.
--
You received this bug notification because you are a member of Ubuntu
High Availability Team, which is subscribed to pacemaker in Ubuntu.
https://bugs.launchpad.net/bugs/1871166
Title:
lrmd
Status update - still waiting on original reporter to perform testing
with -proposed package.
--
You received this bug notification because you are a member of Ubuntu
High Availability Team, which is subscribed to pacemaker in Ubuntu.
https://bugs.launchpad.net/bugs/1871166
Title:
lrmd
The original reporter has performed testing and verified that the
original crash no longer happens with the package in proposed, so I am
marking this as verified.
Please note that a *new* crash has been reported, and is being worked in
bug 1877280. It is *not* a regression caused by the patches
on to bug 1871166.
** Affects: pacemaker (Ubuntu)
Importance: Undecided
Status: Fix Released
** Affects: pacemaker (Ubuntu Xenial)
Importance: Medium
Assignee: Dan Streetman (ddstreet)
Status: In Progress
** Also affects: pacemaker (Ubuntu Xenial)
Importance
** Changed in: systemd (Ubuntu Bionic)
Assignee: (unassigned) => Jorge Niedbalski (niedbalski)
** Changed in: systemd (Ubuntu Bionic)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
High Availability Team, which is subscribed
30 matches
Mail list logo
