[Pacemaker] 1.1.8 not compatible with 1.1.7?

[Pavlos Parissis]

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.

Cheers,
Pavlos


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 901 bytes
Desc: OpenPGP digital signature
URL: <https://lists.clusterlabs.org/pipermail/pacemaker/attachments/20130414/5863f9e1/attachment-0004.sig>