** Changed in: corosync (Ubuntu Precise)
Assignee: Rafael David Tinoco (inaddy) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to corosync in Ubuntu.
https://bugs.launchpad.net/bugs/1318441
Title:
Precise corosync
This bug was fixed in the package corosync - 1.4.2-2ubuntu0.2
---
corosync (1.4.2-2ubuntu0.2) precise; urgency=medium
* Fixed consensus being empty in case failed_to_recv is set (LP: #1318441)
-- Rafael David TinocoMon, 12 May 2014
09:37:06 -0500
** Changed in: corosync (Ubun
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
Server Team, which is subscribed to corosync in Ubuntu.
** Branch linked: lp:ubuntu/precise-proposed/corosync
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to corosync in Ubuntu.
https://bugs.launchpad.net/bugs/1318441
Title:
Precise corosync dies if failed_to_recv is set
To manage notifi
Hello Rafael, or anyone else affected,
Accepted corosync into precise-proposed. The package will build now and
be available at
http://launchpad.net/ubuntu/+source/corosync/1.4.2-2ubuntu0.2 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https
Sponsored for Precise.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to corosync in Ubuntu.
https://bugs.launchpad.net/bugs/1318441
Title:
Precise corosync dies if failed_to_recv is set
To manage notifications about this bug go to:
h
** Also affects: corosync (Ubuntu Precise)
Importance: Undecided
Status: New
** Changed in: corosync (Ubuntu Precise)
Assignee: (unassigned) => Rafael David Tinoco (inaddy)
** Changed in: corosync (Ubuntu)
Status: In Progress => Fix Released
** Changed in: corosync (Ubuntu
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 fe
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
** 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 m
10 matches
Mail list logo
