[Pacemaker] 1.1.8 not compatible with 1.1.7?

[Pavlos Parissis]

Hoi,

I upgraded 1st node and here are the logs
https://dl.dropboxusercontent.com/u/1773878/pacemaker-issue/node1.debuglog
https://dl.dropboxusercontent.com/u/1773878/pacemaker-issue/node2.debuglog

Enabling tracing on the mentioned functions didn't give at least to me any
more information.

Cheers,
Pavlos


On 15 April 2013 01:42, Andrew Beekhof <andrew at beekhof.net> wrote:

>
> On 15/04/2013, at 7:31 AM, Pavlos Parissis <pavlos.parissis at gmail.com>
> wrote:
>
> > On 12/04/2013 09:37 μμ, Pavlos Parissis wrote:
> >> Hoi,
> >>
> >> As I wrote to another post[1] I failed to upgrade to 1.1.8 for a 2 node
> >> cluster.
> >>
> >> Before the upgrade process both nodes are using CentOS 6.3, corosync
> >> 1.4.1-7 and pacemaker-1.1.7.
> >>
> >> I followed the rolling upgrade process, so I stopped pacemaker and then
> >> corosync on node1 and upgraded to CentOS 6.4. The OS upgrade upgrades
> >> also pacemaker to 1.1.8-7 and corosync to 1.4.1-15.
> >> The upgrade of rpms went smoothly as I knew about the crmsh issue so I
> >> made sure I had crmsh rpm on my repos.
> >>
> >> Corosync started without any problems and both nodes could see each
> >> other[2]. But for some reason node2 failed to receive a reply on join
> >> offer from node1 and node1 never joined the cluster. Node1 formed a new
> >> cluster as it never got an reply from node2, so I ended up with a
> >> split-brain situation.
> >>
> >> Logs of node1 can be found here
> >> https://dl.dropboxusercontent.com/u/1773878/pacemaker-issue/node1.log
> >> and of node2 here
> >> https://dl.dropboxusercontent.com/u/1773878/pacemaker-issue/node2.log
> >>
> >
> > Doing a Disconnect & Reattach upgrade of both nodes at the same time
> > brings me a working 1.1.8 cluster. Any attempt to make a 1.1.8 node to
> > join a cluster with a 1.1.7 failed.
>
> There wasn't enough detail in the logs to suggest a solution, but if you
> add the following to /etc/sysconfig/pacemaker and re-test, it might shed
> some additional light on the problem.
>
> export PCMK_trace_functions=ais_dispatch_message
>
> Certainly there was no intention to make them incompatible.
>
> >
> > Cheers,
> > Pavlos
> >
> >
> > _______________________________________________
> > Pacemaker mailing list: Pacemaker at oss.clusterlabs.org
> > http://oss.clusterlabs.org/mailman/listinfo/pacemaker
> >
> > Project Home: http://www.clusterlabs.org
> > Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
> > Bugs: http://bugs.clusterlabs.org
>
>
> _______________________________________________
> Pacemaker mailing list: Pacemaker at oss.clusterlabs.org
> http://oss.clusterlabs.org/mailman/listinfo/pacemaker
>
> Project Home: http://www.clusterlabs.org
> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
> Bugs: http://bugs.clusterlabs.org
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.clusterlabs.org/pipermail/pacemaker/attachments/20130415/635fa79f/attachment-0003.html>