[ClusterLabs] Rolling upgrade from Corosync 2.3+ to Corosync 2.99+ or Corosync 3.0+?

[Vitaly Zolotusky]

Thank you very much for your help!
We did try to go to V3.0.3-5 and then dropped to 2.99 in hope that it may work with rolling upgrade (we were fooled by the same major version (2)). Our fresh install works fine on V3.0.3-5.
Do you know if it is possible to build Pacemaker 3.0.3-5 and Corosync 2.0.3 on Fedora 22 so that I upgrade the stack before starting "real" upgrade of the product? 
Then I can do the following sequence:
1. "quick" full shutdown for HA stack upgrade to 3.0 version
2. start HA stack on the old OS and product version with Pacemaker 3.0.3 and bring the product online
3. start rolling upgrade for product upgrade to the new OS and product version
Thanks again for your help!
_Vitaly

> On June 11, 2020 3:30 AM Jan Friesse <jfriesse at redhat.com> wrote:
> 
>  
> Vitaly,
> 
> > Hello everybody.
> > We are trying to do a rolling upgrade from Corosync 2.3.5-1 to Corosync 2.99+. It looks like they are not compatible and we are getting messages like:
> 
> Yes, they are not wire compatible. Also please do not use 2.99 versions, 
> these were alfa/beta/rc before 3.0 and 3.0 is actually quite a long time 
> released (3.0.4 is latest and I would recommend using it - there were 
> quite a few important bugfixes between 3.0.0 and 3.0.4)
> 
> 
> > Jun 11 02:10:20 d21-22-left corosync[6349]:   [TOTEM ] Message received from 172.18.52.44 has bad magic number (probably sent by Corosync 2.3+).. Ignoring
> > on the upgraded node and
> > Jun 11 01:02:37 d21-22-right corosync[14912]:   [TOTEM ] Invalid packet data
> > Jun 11 01:02:38 d21-22-right corosync[14912]:   [TOTEM ] Incoming packet has different crypto type. Rejecting
> > Jun 11 01:02:38 d21-22-right corosync[14912]:   [TOTEM ] Received message has invalid digest... ignoring.
> > on the pre-upgrade node.
> > 
> > Is there a good way to do this upgrade?
> 
> Usually best way is to start from scratch in testing environment to make 
> sure everything works as expected. Then you can shutdown current 
> cluster, upgrade and start it again - config file is mostly compatible, 
> you may just consider changing transport to knet. I don't think there is 
> any definitive guide to do upgrade without shutting down whole cluster, 
> but somebody else may have idea.
> 
> Regards,
>    Honza
> 
> > I would appreciate it very much if you could point me to any documentation or articles on this issue.
> > Thank you very much!
> > _Vitaly
> > _______________________________________________
> > Manage your subscription:
> > https://lists.clusterlabs.org/mailman/listinfo/users
> > 
> > ClusterLabs home: https://www.clusterlabs.org/
> >