[ClusterLabs] SLES11SP4 and SLES12 SP4: different crypto type

[Ulrich Windl]

Hi!

I'm playing with upgrading a SLES11 SP4 cluster to SLES12 SP4. After having upgraded on node in a two-node cluster, I see the following messages on the SLES12 node:

[...]
Feb 27 08:46:16 h02 corosync[5198]:   [TOTEM ] A new membership (172.20.16.2:2336) was formed. Members joined: 739512322
Feb 27 08:46:16 h02 corosync[5198]:   [MAIN  ] Completed service synchronization, ready to provide service.
Feb 27 08:46:16 h02 corosync[5198]:   [TOTEM ] Incoming packet has different crypto type. Rejecting
Feb 27 08:46:16 h02 corosync[5198]:   [TOTEM ] Received message has invalid digest... ignoring.
Feb 27 08:46:16 h02 corosync[5198]:   [TOTEM ] Invalid packet data
Feb 27 08:46:16 h02 corosync[5192]: Starting Corosync Cluster Engine (corosync): [  OK  ]
[...]
Feb 27 08:46:29 rksaph02 corosync[5198]:   [TOTEM ] Incoming packet has different crypto type. Rejecting
Feb 27 08:46:29 rksaph02 corosync[5198]:   [TOTEM ] Received message has invalid digest... ignoring.
[...]

The last two messages repeating rapidly, so I stopped the node after a few seconds.

On the SLES11 node I see these messages:
Feb 27 08:46:16 h06 corosync[9337]:   [TOTEM ] Received message has invalid digest... ignoring.
Feb 27 08:46:16 h06 corosync[9337]:   [TOTEM ] Invalid packet data
[...]

I wonder: Is this incompatibility by design, or did SUSE packaging create the mess (they did a terrible thing with the OpenLDAP packages)? Is there a chance for a rolling cluster upgrade?

Regards,
Ulrich