Re: [Pacemaker] 1.1.8 not compatible with 1.1.7?

Fri, 03 May 2013 03:53:47 -0700

Now i have all the logs for some combinations.
 
Corosync: 1.4.1-7 for all the tests on all nodes
Base is always fresh installation of each node with all packages equal except pacemaker version.
int2node1 node id: 1743917066
int2node2 node id: 1777471498
 
In each ZIP file log from both nodes and the status output of crm_mon and cibadmin -Q is  included.
 
1.) 1.1.8-4 attaches to running 1.1.7-6 cluster
https://www.dropbox.com/s/06oyrle4ny47uv9/attach_1.1.8-4_to_1.1.7-6.zip
Result: join outstanding
 
2.) 1.1.9-2 attaches to running 1.1.7-6 cluster
https://www.dropbox.com/s/fv5kcm2yb5jz56z/attach_1.1.9-2_to_1.1.7-6.zip
Result: join outstanding
 
3.) 1.1.9-2 attaches to running 1.1.8-4 cluster
https://www.dropbox.com/s/y9o4yo8g8ahwjga/attach_1.1.9-2_to_1.1.8-4.zip
Result: join successful
 
Rainer
Gesendet: Freitag, 03. Mai 2013 um 01:30 Uhr
Von: "Andrew Beekhof" <and...@beekhof.net>
An: "The Pacemaker cluster resource manager" <pacemaker@oss.clusterlabs.org>
Betreff: Re: [Pacemaker] 1.1.8 not compatible with 1.1.7?

On 03/05/2013, at 4:46 AM, Rainer Brestan <rainer.bres...@gmx.net> wrote:

> Hi Lars,
> i have tried 1.1.9-2 from download area at clusterlabs for RHEL6 with corosync 1.4.1-17, also running with 1.1.7-6 at the other node.
> I have to go deeper in details later on (with logs), but the first try was worse than 1.1.8-7.
> When the node with 1.1.9-2 joins the cluster, it could not even decode the ais_message to get the node name of the node running 1.1.7-6.

Logs?

> It states a new node has joined with the correct node id, but as name it could only decode (null) as node name.
>
> Just as first impression.
>
> Rainer
>
> Gesendet: Dienstag, 30. April 2013 um 17:16 Uhr
> Von: "Lars Marowsky-Bree" <l...@suse.com>
> An: pacemaker@oss.clusterlabs.org
> Betreff: Re: [Pacemaker] 1.1.8 not compatible with 1.1.7?
> On 2013-04-24T11:44:57, Rainer Brestan <rainer.bres...@gmx.net> wrote:
>
> > Current DC: int2node2 - partition WITHOUT quorum
> > Version: 1.1.8-7.el6-394e906
>
> This may not be the answer you want, since it is fairly unspecific. But
> I think we noticed something similar when we pulled in 1.1.8, I don't
> recall the bug number, but I *think* it worked out with a later git
> version.
>
> Can you try a newer build than 1.1.8?
>
>
> Regards,
> Lars
>
> --
> Architect Storage/HA
> SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 21284 (AG Nürnberg)
> "Experience is the name everyone gives to their mistakes." -- Oscar Wilde
>
>
> _______________________________________________
> Pacemaker mailing list: Pacemaker@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@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@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@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

Reply via email to