** Changed in: pacemaker (Ubuntu)
Status: New = In Progress
--
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/1312156
Title:
[Precise] Potential for data
** Changed in: pacemaker (Ubuntu)
Assignee: (unassigned) = Rafael David Tinoco (inaddy)
--
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/1312156
Title:
[Precise
Here is the patch fixing corosync misbehavior described above.
Description: Remove buggy logic to prevent secondary dc fencing
On logic before commit 82aa2d8d17 the node responsible for fencing
(executioner) the dc was responsible also for updating cib. If this
update failed (due to a
** Description changed:
+ [Impact]
+
+ * Pacemaker designated controller can make wrong decisions based on
+ uncleared node status on a rare specific situation. This situation can
+ make the same resource starts on two nodes at the same time, resulting
+ in data corruption.
+
+ [Test Case]
+
Public bug reported:
If node detects itself not able to receive message it asserts the number of
failed members considering itself and dies.
I'll write more information (and the fix) in a few minutes.
** Affects: corosync (Ubuntu)
Importance: Undecided
Assignee: Rafael David Tinoco
** Description changed:
- If node detects itself not able to receive message it asserts the number of
failed members considering itself and dies.
- I'll write more information (and the fix) in a few minutes.
+ If node detects itself not able to receive message it asserts the number
+ of failed
Attaching patch.
** Patch added: corosync_1.4.2-2ubuntu0.2.diff
https://bugs.launchpad.net/ubuntu/+source/corosync/+bug/1318441/+attachment/4110673/+files/corosync_1.4.2-2ubuntu0.2.diff
** Description changed:
[Impact]
- * On certain conditions corosync daemon may quit if it detects
Tests before the patch:
#
# NODE 1
#
--- MARKER --- ./failed-to-receive-crash.sh at 2014-05-09-17:33:04 --- MARKER
---
May 09 17:33:04 corosync [MAIN]: ] Corosync Cluster Engine ('1.4.2'): started
and ready to provide service.
May 09 17:33:04 corosync [MAIN]: ] Corosync built-in
Brian,
I've made several tests on this and everything works like expected.
Changing tag.
Thanks
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
High Availability Team, which is subscribed to
** Changed in: pacemaker (Ubuntu Precise)
Assignee: Rafael David Tinoco (inaddy) = (unassigned)
--
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/1312156
Title
** Changed in: corosync (Ubuntu Precise)
Assignee: Rafael David Tinoco (inaddy) = (unassigned)
--
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/1318441
Title
## After applying the fix I could successfully put one node on standby.
Resources migrated correctly.
root@trustycluster02:~# crm_mon
Connection to the CIB terminated
Reconnecting...root@trustycluster02:~# crm_mon -1
Last updated: Wed Aug 6 10:27:35 2014
Last change: Tue Aug 5 15:42:11 2014 via
Created one public PPA so the SRU proposal can be tested before asking
for sponsorship:
https://launchpad.net/~inaddy/+archive/ubuntu/lp1353473
# apt-add-repository ppa:inaddy/lp1353473
# apt-get update
# apt-get dist-upgrade
* attention: this will replace current trusty pacemaker version:
** Description changed:
[Impact]
* Whenever a user uses crm node standby the code can make lrmd still
-try to monitor resource put into stand-by and cause error messages.
+ try to monitor resource put into stand-by and cause error messages.
[Test Case]
* To use crm node
Uploading fix for Trusty (corrected upstream commit #s).
** Patch added: trusty_pacemaker_1.1.10+git20130802-1ubuntu3.debdiff
https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1353473/+attachment/4172984/+files/trusty_pacemaker_1.1.10%2Bgit20130802-1ubuntu3.debdiff
--
You received
inaddy@trusty.00070403:/bugs/00070403/sources/upstream$ git tag --contains
48f90f6
inaddy@trusty.00070403:/bugs/00070403/sources/upstream$ git tag --contains
c29ab27
inaddy@trusty.00070403:/bugs/00070403/sources/upstream$ git tag --contains
348bb51
Pacemaker-1.1.12
Pacemaker-1.1.12-rc1
Attaching Trusty fix.
** Patch added: trusty_pacemaker_1.1.10+git20130802-1ubuntu3.debdiff
https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1353473/+attachment/4173016/+files/trusty_pacemaker_1.1.10%2Bgit20130802-1ubuntu3.debdiff
--
You received this bug notification because you are
Attaching Utopic fix.
** Patch added: utopic_pacemaker_1.1.10+git20130802-4ubuntu3.debdiff
https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1353473/+attachment/4173017/+files/utopic_pacemaker_1.1.10%2Bgit20130802-4ubuntu3.debdiff
--
You received this bug notification because you are
Proposed merge to Utopic:
https://code.launchpad.net/~inaddy/ubuntu/utopic/pacemaker/bug-1353473/+merge/230169
--
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/1353473
** Summary changed:
- Trusty Pacemaker crm node standby stops resource successfully, but lrmd
still monitors it and causes Failed actions
+ Pacemaker crm node standby stops resource successfully, but lrmd still
monitors it and causes Failed actions
--
You received this bug notification
Submitted fix to Debian:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=757514
Waiting for fix/merge.
** Bug watch added: Debian Bug tracker #757514
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=757514
--
You received this bug notification because you are a member of Ubuntu
High
** Also affects: pacemaker (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=757514
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
High Availability Team, which is subscribed to pacemaker in Ubuntu.
Public bug reported:
It was brought to my attention the following situation:
[Issue]
lrmd process crashed when repeating crm node standby and crm node
online
# grep pacemakerd ha-log.k1pm101 | grep core
Aug 27 17:47:06 k1pm101 pacemakerd[49271]: error: child_waitpid:
)
* Fix: services: Fix the executing of synchronous actions - 2/2 (LP: #1368737)
-- Rafael David Tinoco rafael.tin...@canonical.com Fri, 12 Sep 2014
15:52:14 -0300
pacemaker (1.1.10+git20130802-1ubuntu3) trusty; urgency=medium
* Fix: services: Do not allow duplicate recurring op entries - 1/3 (LP
- 1 root root 443K Oct 30 01:21 _usr_lib_pacemaker_stonithd.0.crash
** Changed in: pacemaker (Ubuntu)
Assignee: (unassigned) = Rafael David Tinoco (inaddy)
** Attachment added: cib.xml
https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1368737/+attachment/4249543/+files/cib.xml
Trusty is affected and Precise is NOT.
libglib2.0-0 | 2.24.0-0ubuntu4 | lucid| amd64, armel, i386, ia64,
powerpc, sparc
libglib2.0-0 | 2.24.1-0ubuntu2 | lucid-updates| amd64, armel, i386, ia64,
powerpc, sparc
libglib2.0-0 | 2.32.1-0ubuntu2 | precise | amd64, armel,
Analyzing the stacktrace for stonithd:
(gdb) bt
#0 0x7fed094febb9 in __GI_raise (sig=sig@entry=6) at
../nptl/sysdeps/unix/sysv/linux/raise.c:56
#1 0x7fed09501fc8 in __GI_abort () at abort.c:89
#2 0x7fed0a15a6c9 in crm_abort (file=0x7fed0a17e4bb logging.c,
Utopic Fix.
** Patch added: utopic_pacemaker_1.1.10+git20130802-4ubuntu4.debdiff
https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1368737/+attachment/4249614/+files/utopic_pacemaker_1.1.10%2Bgit20130802-4ubuntu4.debdiff
--
You received this bug notification because you are a member
Running testcase for some time and couldn't get any core dump...
Services seem stable:
Every 1.0s: crm_mon -1
Fri Oct 31 00:52:57 2014
Last updated: Fri Oct 31 00:52:57 2014
Last change: Fri Oct 31 00:31:22 2014 via crm_attribute on clustertrusty04
Stack: corosync
Current DC: clustertrusty02
Trusty Fix.
** Patch added: trusty_pacemaker_1.1.10+git20130802-1ubuntu2.2.debdiff
https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1368737/+attachment/4249612/+files/trusty_pacemaker_1.1.10%2Bgit20130802-1ubuntu2.2.debdiff
--
You received this bug notification because you are a
Vivid might also need a fix/update to proper handle this.
** Changed in: pacemaker (Ubuntu)
Status: Confirmed = In Progress
--
You received this bug notification because you are a member of Ubuntu
High Availability Team, which is subscribed to pacemaker in Ubuntu.
I'm asking for sponsorship for this...
Meanwhile I have created one PPA to be used:
https://launchpad.net/~inaddy/+archive/ubuntu/lp1368737
# add-apt-repository ppa:inaddy/lp1368737
# apt-get update
# apt-get install pacemaker
The right package version, for now, will be:
** Description changed:
+ [IMPACT]
+
+ - Pacemaker seg fault on repeated crm node online/standy because:
+ - Newer glib versions uses hash_table to find GSources
+ - Glib can try to assert source being removed multiple times
+
+ [TEST CASE]
+
+ - Using same configuration as
** Changed in: pacemaker (Ubuntu Trusty)
Assignee: (unassigned) = Rafael David Tinoco (inaddy)
** Changed in: pacemaker (Ubuntu)
Assignee: (unassigned) = Rafael David Tinoco (inaddy)
--
You received this bug notification because you are a member of Ubuntu
High Availability Team, which
** Changed in: pacemaker (Ubuntu)
Status: New = In Progress
** Changed in: pacemaker (Ubuntu Trusty)
Status: New = In Progress
--
You received this bug notification because you are a member of Ubuntu
High Availability Team, which is subscribed to pacemaker in Ubuntu.
Considering bug:
https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1382842
I'll have to fix dependencies together with this SRU.
Please hold while I fix this new debdiff (for this case), fixing lib
dependencies for pacemaker to be upgraded.
Thank you
Rafael Tinoco
--
You received
** Summary changed:
- Pacemaker can seg fault on crm node online/standy
+ Pacemaker can seg fault on crm node online/standby
--
You received this bug notification because you are a member of Ubuntu
High Availability Team, which is subscribed to pacemaker in Ubuntu.
It looks like the format chosen for SRU for this package :
pacemaker (1.1.10+git20130802-1ubuntu2.1) trusty
pacemaker (1.1.10+git20130802-1ubuntu2) trusty
pacemaker (1.1.10+git20130802-1ubuntu1) saucy
makes dh helpers not to calculate shlibs version properly:
$ fakeroot dh_makeshlibs -a -V
$
The way this package's versioning was made makes the tool
dh_makeshlibs (debian helper) not to append proper suffix to
dependencies (using (= 1.1.10+git20130802) instead of (=
1.1.10+git20130802-1ubuntu2.1) for example).
I changed debian/rules so the proper version is considered for
dependencies:
Trusty fix.
** Patch added: trusty_pacemaker_1.1.10+git20130802-1ubuntu2.2.debdiff
https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1368737/+attachment/4258483/+files/trusty_pacemaker_1.1.10%2Bgit20130802-1ubuntu2.2.debdiff
--
You received this bug notification because you are a
Utopic fix.
** Patch added: utopic_pacemaker_1.1.10+git20130802-4ubuntu4.debdiff
https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1368737/+attachment/4258484/+files/utopic_pacemaker_1.1.10%2Bgit20130802-4ubuntu4.debdiff
--
You received this bug notification because you are a member
I recommend, if possible, Vivid to use 1.1.12 (from upstream) and to use
a different versioning scheme.
Asking for sponsorship.
Thank you
Rafael Tinoco
--
You received this bug notification because you are a member of Ubuntu
High Availability Team, which is subscribed to pacemaker in Ubuntu.
Hello Peter,
Could you test version ~2 ? I'm uploading it to the PPA right now.
I backported some other fixes regarding the same issue.
Waiting on your feedback.
Thanks for reporting!!!
Rafael Tinoco
--
You received this bug notification because you are a member of Ubuntu
High Availability
** Tags removed: verification-needed
** Tags added: verification-done
--
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/1382842
Title:
pacemaker should have a binary
Peter,
Can you help verifying this package from -proposed ?
After installing the package from -proposed, could you check if your
cluster is:
1) operational
2) resources are ok
3) fencing correctly
4) no more segfaults from lrmd and/or stonith
Waiting for feedback so we can change this to
Okay,
So the cherry-pick (for version
trusty_pacemaker_1.1.10+git20130802-1ubuntu2.2, based on a upstream
commit) seems ok since it makes lrmd (services, services_linux) to avoid
repeating a timer when the source was already removed from glib main
loop context:
example:
+ if
for feedback.
** Affects: pacemaker (Ubuntu)
Importance: Undecided
Assignee: Rafael David Tinoco (inaddy)
Status: In Progress
** Tags: cts
** Changed in: pacemaker (Ubuntu)
Assignee: (unassigned) = Rafael David Tinoco (inaddy)
** Summary changed:
- Stonith can seg fault
Peter,
Since the bug you are reporting is related to stonith, I'm separating
two cases:
LP: #1368737 -- Pacemaker (lrmd) can seg fault in Trusty and Utopic
after following message: Source ID XX was not found when attempting to
remove
And
LP: #1412962 -- Pacemaker (stonith) can seg fault in
Peter,
I have created one PPA to be tested:
https://launchpad.net/~inaddy/+archive/ubuntu/lp1412962
# add-apt-repository ppa:inaddy/lp1412962
# apt-get update
# apt-get install pacemaker
The right package version, for now, will be:
1.1.10+git20130802-1ubuntu2.3~lp1412962~1 (for Trusty)
And
Peter,
(1) During the test execution, does using more then 2 nodes AND/OR
changing no-quorum-policy to something else (freeze, stop, suicide)
does help ?
(2) Your crash files do not contain the core file, could you please
provide me the core file (probably changing ulimit inside
I just found one upstream commit fixing this:
##
commit 0326f05c9e26f39a394fa30830e31a76306f49c7
Author: Andrew Beekhof and...@beekhof.net
Date: Thu Aug 7 13:49:24 2014 +1000
Fix: stonith-ng: Reset mainloop source IDs after removing them
diff --git a/lib/fencing/st_client.c
Peter,
We are getting feedback from others saying that this indeed fixed their setups
also.
Mind if I consider this verification-done since it would be good to push such
a fix soon.
Tks
Tinoco
--
You received this bug notification because you are a member of Ubuntu
High Availability Team,
Subscribing sponsors-team. Asking sponsorship.
--
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/1412962
Title:
Pacemaker (stonith) can seg fault in Trusty and Utopic
Attaching fix for Trusty
** Patch added: trusty_pacemaker_1.1.10+git20130802-1ubuntu2.3.debdiff
https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1412962/+attachment/4306494/+files/trusty_pacemaker_1.1.10%2Bgit20130802-1ubuntu2.3.debdiff
--
You received this bug notification because
Brian Murray or James Pages,
I verified this fix for the test case in the description and it worked
fine. Meanwhile I had some complains from Peter regarding crashes he was
getting into his installation. I opened the following bug:
https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1412962
** Description changed:
+
+ [IMPACT]
+
+ - Pacemaker seg fault (stonith and lrmd) because:
+ - Newer glib versions uses hash_table to find GSources
+ - Glib can try to assert source being removed multiple times
+
+ [TEST CASE]
+
+ - Described by user
+
+ [REGRESSION
Attaching fix for Utopic
** Patch added: utopic_pacemaker_1.1.10+git20130802-4ubuntu3.2.debdiff
https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1412962/+attachment/4306495/+files/utopic_pacemaker_1.1.10%2Bgit20130802-4ubuntu3.2.debdiff
--
You received this bug notification because
** No longer affects: pacemaker (Debian)
--
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/1353473
Title:
Pacemaker crm node standby stops resource successfully, but lrmd
** Changed in: pacemaker (Ubuntu Trusty)
Assignee: Rafael David Tinoco (inaddy) = (unassigned)
** Changed in: pacemaker (Ubuntu Vivid)
Assignee: Rafael David Tinoco (inaddy) = (unassigned)
--
You received this bug notification because you are a member of Ubuntu
High Availability Team
Thanks Chris,
Doing that right now and re-attaching debdiffs for Vivid.
Thanks for reviewing all this.
-Rafael
** Patch removed: vivid_libibverbs_1.1.8-1ubuntu2.debdiff
Re-attaching vivid debdiffs (with corrections proposed by Chris Arges)
--
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/1409904
Title:
Needed patches for InfiniBand
vivid_libmlx4_1.0.6-1ubuntu0.1.debdiff
** Patch added: vivid_libmlx4_1.0.6-1ubuntu0.1.debdiff
https://bugs.launchpad.net/ubuntu/+source/libibverbs/+bug/1409904/+attachment/4392209/+files/vivid_libmlx4_1.0.6-1ubuntu0.1.debdiff
--
You received this bug notification because you are a member of
vivid_tgt_1.0.43-0ubuntu4.1.debdiff
** Patch added: vivid_tgt_1.0.43-0ubuntu4.1.debdiff
https://bugs.launchpad.net/ubuntu/+source/libibverbs/+bug/1409904/+attachment/4392210/+files/vivid_tgt_1.0.43-0ubuntu4.1.debdiff
--
You received this bug notification because you are a member of Ubuntu
wily_libmlx4_1.0.6-1ubuntu1.debdiff
** Patch added: wily_libmlx4_1.0.6-1ubuntu1.debdiff
https://bugs.launchpad.net/ubuntu/+source/libibverbs/+bug/1409904/+attachment/4393171/+files/wily_libmlx4_1.0.6-1ubuntu1.debdiff
--
You received this bug notification because you are a member of Ubuntu
wily_libibverbs_1.1.8-1ubuntu2.debdiff
** Patch added: wily_libibverbs_1.1.8-1ubuntu2.debdiff
https://bugs.launchpad.net/ubuntu/+source/libibverbs/+bug/1409904/+attachment/4393170/+files/wily_libibverbs_1.1.8-1ubuntu2.debdiff
--
You received this bug notification because you are a member of
= Invalid
** Changed in: qpid-cpp (Ubuntu Trusty)
Assignee: Rafael David Tinoco (inaddy) = (unassigned)
--
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/1409904
Title
** Changed in: corosync (Ubuntu Trusty)
Status: New = Invalid
** Changed in: corosync (Ubuntu Trusty)
Assignee: Rafael David Tinoco (inaddy) = (unassigned)
** Changed in: fio (Ubuntu Trusty)
Status: New = Invalid
** Changed in: fio (Ubuntu Trusty)
Assignee: Rafael David
Packages libiverbs and libmlx4 do not break ABI compatibility thus
rdepends do not need to be recompiled.
The abi_compat field of struct ibv_context is used to determine
support of verbs extensions. As a result, support for ABI version 2
is removed (corresponds to kernel releases 2.6.11-2.6.14
libmlx4 does need specific version from libibverbs because it is also
being changed to support:
- Flow steering control
- Offload support
thus this version, 1.0.5-1ubuntu2 has to be compiled exactly with
libibverbs-dev (= 1.1.7-1ubuntu2) and depends exactly on libibverbs1
(= 1.1.7-1ubuntu2).
** Changed in: perftest (Ubuntu Trusty)
Status: New = Invalid
** Changed in: perftest (Ubuntu Trusty)
Assignee: Rafael David Tinoco (inaddy) = (unassigned)
--
You received this bug notification because you are a member of Ubuntu
High Availability Team, which is subscribed
= In Progress
** Changed in: openmpi (Ubuntu Trusty)
Status: In Progress = Invalid
** Changed in: openmpi (Ubuntu Trusty)
Assignee: Rafael David Tinoco (inaddy) = (unassigned)
** Changed in: libmlx4 (Ubuntu Trusty)
Status: New = In Progress
** Changed in: libibverbs (Ubuntu
--
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/1409904
Title:
Needed patches for InfiniBand Support: Flow Steering and Offload
Support + Fixes
Status in corosync
Hello Sponsors,
I'd like to know if it is possible for us to upload fixes for Trusty,
Vivid, Utopic since Wily was fixed sometime ago.
Thank you.
Rafael Tinoco
** Tags removed: cts
** Tags added: sts
--
You received this bug notification because you are a member of Ubuntu
High Availability
** Changed in: fio (Ubuntu)
Assignee: (unassigned) = Rafael David Tinoco (inaddy)
** Changed in: fio (Ubuntu Trusty)
Assignee: (unassigned) = Rafael David Tinoco (inaddy)
** Changed in: glusterfs (Ubuntu)
Assignee: (unassigned) = Rafael David Tinoco (inaddy)
** Changed
** Changed in: libmlx4 (Ubuntu Vivid)
Assignee: (unassigned) = Rafael David Tinoco (inaddy)
** Changed in: libmlx5 (Ubuntu)
Assignee: (unassigned) = Rafael David Tinoco (inaddy)
** Changed in: libmlx5 (Ubuntu Trusty)
Assignee: (unassigned) = Rafael David Tinoco (inaddy
** Changed in: libmlx5 (Ubuntu)
Status: New = Invalid
** Changed in: libmlx5 (Ubuntu)
Assignee: Rafael David Tinoco (inaddy) = (unassigned)
** Changed in: libmthca (Ubuntu)
Status: New = Invalid
** Changed in: libmthca (Ubuntu)
Assignee: Rafael David Tinoco (inaddy
Kamal, Pankaj,
I’m glad to inform that finally bug LP: #1409904 is being finalised (for
Trusty) and its fix is already committed.
Next step is for us to “verify” the fix (from -proposed repository) and
mark the public bug as “verified”.
I have already verified TGT iSER support:
Hello Pankaj,
I’m sorry for not being more clear…
There is no way that a SRU is accepted if -proposed package is not
verified.
TGT iSER support was already verified by me.
I still need Kamal to verify libibverbs and libmlx4.
Thank you!
--
You received this bug notification because you are a
In a meeting with Mellanox in Israel I was told that libibverbs and
libmlx4 have been verified and proved to work. Changing this to
verification done. Thank you.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member
** Changed in: corosync (Ubuntu)
Status: Confirmed => Incomplete
** Changed in: corosync (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
High Availability Team, which is subscribed to corosync in Ubuntu.
results in leak of /dev/shm
space.
Expected results:
No leak
Additional info:
"""
** Affects: corosync (Ubuntu)
Importance: Undecided
Assignee: Rafael David Tinoco (inaddy)
Status: Confirmed
** Changed in: corosync (Ubuntu)
Status: New => Confirmed
**
https://bugzilla.redhat.com/show_bug.cgi?id=1117911
** Bug watch added: Red Hat Bugzilla #1117911
https://bugzilla.redhat.com/show_bug.cgi?id=1117911
--
You received this bug notification because you are a member of Ubuntu
High Availability Team, which is subscribed to corosync in Ubuntu.
Those fixes are already included in corosync v2.3.4:
$ git tag --contains cc80c8567d6eec1d136f9e85d2f8dfb957337eef
v2.3.4
v2.3.5
$ git tag --contains 384760cb670836dc37e243f594612c6e68f44351
v2.3.4
v2.3.5
$ git tag --contains dfaca4b10a005681230a81e229384b6cd239b4f6
v2.3.4
v2.3.5
Fix for Trusty.
** Patch added: "trusty_corosync_2.3.3-1ubuntu2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/corosync/+bug/1530837/+attachment/4549322/+files/trusty_corosync_2.3.3-1ubuntu2.debdiff
--
You received this bug notification because you are a member of Ubuntu
High
BTW,
I provided a public PPA:
https://launchpad.net/~inaddy/+archive/ubuntu/lp1530837
If anyone suffering from this is interested in having a hotfix while SRU
isn't ready.
Thank you
--
You received this bug notification because you are a member of Ubuntu
High Availability Team, which is
** Description changed:
+ [Impact]
+
+ * corosync has a memory leak problem with multiple calls to corosync -v
+ * corosync has a memory leak problem by not properly handling signals
+
+ [Test Case]
+
+ * run "corosync -v" multiple times
+ * some cloud tools do that
+
+ [Regression
** Changed in: corosync (Ubuntu Trusty)
Status: New => Confirmed
** Changed in: corosync (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: corosync (Ubuntu Trusty)
Assignee: (unassigned) => Rafael David Tinoco (inaddy)
** Changed in: corosync (Ubuntu)
Waiting for the BUG to be sponsored.
Thank you.
--
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/1530837
Title:
Logsys file leaks in /dev/shm after sigabrt, sigsegv and
Hello Mark,
Tks for reviewing my mistake. I believe it is good now.
inaddy@lp1530837trusty:~/Codes/bugs/1530837/trusty/corosync-2.3.3$ patch -p1 <
../trusty_corosync_2.3.3-1ubuntu2.debdiff
patching file debian/changelog
patching file
** Patch removed: "trusty_corosync_2.3.3-1ubuntu2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/corosync/+bug/1530837/+attachment/4549322/+files/trusty_corosync_2.3.3-1ubuntu2.debdiff
** Changed in: corosync (Ubuntu Trusty)
Status: Incomplete => In Progress
** Patch added:
Is systemd's sysv-generator prioritized over regular systemd unit files
? My question raises from this fix. It looks like unit files were
automatically created because of the existence of the wrong LSB
parameters in init files - by the generator - but at the same time
Xenial should be using
** Tags added: ubuntu-ha
--
You received this bug notification because you are a member of Ubuntu
High Availability Team, which is subscribed to ocfs2-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1584629
Title:
Failed to start LSB: Load O2CB cluster services at system boot.
Status in
** Tags added: ubuntu-ha
** Changed in: ocfs2-tools (Ubuntu)
Status: New => Incomplete
** Changed in: ocfs2-tools (Ubuntu)
Status: Incomplete => Confirmed
** Changed in: ocfs2-tools (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are
That change would have to have happened in Nautilus, since the "external
helpers" feature is something done by the "umount" utility, which
redirects the umount requests to a wrapper (helper), but, before,
removing the uhelper flag from the umount requested.
I'm marking this as "won't fix" because
This has been upstreamed long time ago:
commit faa022c14609d74b39498970f9a444a3d05ec080
Author: Ante Karamatić
Date: Fri Feb 17 05:25:46 2012
Medium: LRM: lrmd: use the resource timeout as an override to the
default dbus timeout for upstart RA
and this bug can be closed as Fix Released.
Its it not clear which bug was pointed out. An upstream patch was given
and, right now, all I can do is to guarantee that this patch is, still,
contained in cluster-glue upstream version:
} else {
if (HA_OK !=
ha_msg_mod_int(op->msg,F_LRM_OPSTATUS,(int)LRM_OP_CANCELLED)) {
** Tags added: ubuntu-ha
--
You received this bug notification because you are a member of Ubuntu
High Availability Team, which is subscribed to ocfs2-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1412438
Title:
OCF:pacemaker:o2cb broken in 14.04
Status in ocfs2-tools package in Ubuntu:
** Changed in: cluster-glue (Ubuntu)
Assignee: (unassigned) => Rafael David Tinoco (rafaeldtinoco)
** Tags added: ubuntu-ha
--
You received this bug notification because you are a member of Ubuntu
High Availability Team, which is subscribed to cluster-glue in Ubuntu.
ht
Since Trusty is EOL, and the current upstream version contains the
pointed fix:
inaddy@workstation:~/work/sources/upstream/cluster-glue$ git log --grep
"replace experimental smart"
commit a182a0dd9fa41f0b1c0ceb50dc97a9b3e379564c
Author: Dejan Muhamedagic
Date: Mon Nov 3 13:33:57 2014
** Changed in: cluster-glue (Ubuntu)
Assignee: (unassigned) => Rafael David Tinoco (rafaeldtinoco)
** Tags added: ubuntu-ha
--
You received this bug notification because you are a member of Ubuntu
High Availability Team, which is subscribed to cluster-glue in Ubuntu.
ht
1 - 100 of 323 matches
Mail list logo
