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 Tinoco <[email protected]>   Mon, 12 May 2014 
09:37:06 -0500

** Changed in: corosync (Ubuntu Precise)
       Status: Fix Committed => Fix Released

-- 
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:
  Precise corosync dies if failed_to_recv is set

Status in “corosync” package in Ubuntu:
  Fix Released
Status in “corosync” source package in Precise:
  Fix Released

Bug description:
  [Impact]

   * On certain conditions *precise* corosync daemon may quit if it detects 
itself 
     as not being able to receive messages. The logic asserts the existence of 
     at least one functional node but the node is marking itself as a failed 
node 
     (not following the specification). It is safe not to assert this if
     failed_to_recv is set.

  [Test Case]

   * Using "corosync test suite" on precise-test machine:

     - Make sure to set ssh keys so precise-test can access 
precise-cluster-{01,02}.
     - Make sure only failed-to-receive-crash.sh is executable on "tests" dir.
     - Make sure precise-cluster-{01,02} nodes have build-dep for corosync 
installed.
     - sudo ./run-tests.sh -c flatiron -n "precise-cluster-01 
precise-cluster-02"
     - Check corosync log messages to see precise-cluster-01 corosync dieing.

  [Regression Potential]

   * We are not asserting the existence of at least 1 node in corosync cluster
     anymore. Since there is always 1 node in the cluster (the node itself) it
     is very unlikely this change alters corosync logic for membership. If it
     does it is likely corosync will recover from the error and reestablish new
     membership (with 1 or more nodes).

  [Other Info]

   * n/a

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/corosync/+bug/1318441/+subscriptions

_______________________________________________
Mailing list: https://launchpad.net/~ubuntu-ha
Post to     : [email protected]
Unsubscribe : https://launchpad.net/~ubuntu-ha
More help   : https://help.launchpad.net/ListHelp

Reply via email to