This bug was fixed in the package pacemaker - 1.1.6-2ubuntu3.3
---
pacemaker (1.1.6-2ubuntu3.3) precise; urgency=high
* Removed buggy logic that tried to prevent rare secondary dc fencing (LP:
#1312156)
-- Rafael David Tinoco rafael.tin...@canonical.com Fri, 02 May 2014
** Changed in: pacemaker (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 pacemaker in Ubuntu.
https://bugs.launchpad.net/bugs/1312156
Title:
[Precise]
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 pacemaker in
Hello Peter, or anyone else affected,
Accepted pacemaker into precise-proposed. The package will build now and
be available at
http://launchpad.net/ubuntu/+source/pacemaker/1.1.6-2ubuntu3.3 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
** Branch linked: lp:ubuntu/precise-proposed/pacemaker
--
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
Uploaded
--
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:
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
** Also affects: pacemaker (Ubuntu Precise)
Importance: Undecided
Status: New
** Changed in: pacemaker (Ubuntu Precise)
Assignee: (unassigned) = Rafael David Tinoco (inaddy)
** Changed in: pacemaker (Ubuntu)
Assignee: Rafael David Tinoco (inaddy) = (unassigned)
** Changed
** 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]
+
** Changed in: pacemaker (Ubuntu)
Assignee: (unassigned) = Rafael David Tinoco (inaddy)
--
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
** Changed in: pacemaker (Ubuntu)
Status: New = In Progress
--
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
11 matches
Mail list logo