[Pacemaker] Pacemaker 1.1.7 and negative corosync nodeid

Andrew Beekhof andrew at beekhof.net
Sun Aug 25 19:26:32 EDT 2013

On 24/08/2013, at 5:26 AM, Nate Clark <nate at neworld.us> wrote:

> I have a few systems running pacemaker 1.1.7 using corosync and some of them hit the issue that the nodeid in the cib is recorded as a negative number. This issue was resolved in commit f0e9b262f1d3219df248a5340771f8e23c5d6bce. However if you upgrade pacemaker to 1.1.8, the new pacemaker now sees two nodes for every node that hit this issue. It sees one with the negative nodeid and one with the positive.
> Is there a way to prevent this from happening when upgrading from 1.1.7? One way I can think of doing this would be to edit the cib while pacemaker is down so that when it comes up the values are now positive but I am not sure of a way to do that because of the cib signing.

Once the cluster is running again, you can "just" clear out the old entries with: cibadmin --replace --xml-text '<nodes/>'
That should be enough IIRC
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 841 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <https://lists.clusterlabs.org/pipermail/pacemaker/attachments/20130826/84562db7/attachment-0003.sig>

More information about the Pacemaker mailing list