[Bug 1312156] Re: [Precise] Potential for data corruption

[Rafael David Tinoco]

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 executioner fail, for ex) the dc would be
fenced a second time because the cluster would not know about fencing
result.

On upstream commit 82aa2d8d17, a logic trying to avoid this second
dc fencing was introduced. If this node was not the dc fence executioner
it would keep its name. With its name, in the case executioner node
died and this node became the new dc it would be able to update cib
telling the result of last dc fencing. Problem is that this list
is never cleaned and there might be cases wrong cib update is given
(when a dc takeover has to run) resulting in a bad, bad thing: same
resource running on different nodes.

It is much more acceptable for SRU to restore old behavior, known to
be safe even if it implies killing dc twice, than to backport several
pieces of code to implement a logic that was not there on the stable
version release.

** Patch added: "precise_pacemaker_1.1.6-2ubuntu3.3.diff"
   https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1312156/+attachment/4103593/+files/precise_pacemaker_1.1.6-2ubuntu3.3.diff

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to pacemaker in Ubuntu.
https://bugs.launchpad.net/bugs/1312156

Title:
  [Precise] Potential for data corruption

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