[ClusterLabs] Antw: [EXT] Which verson of pacemaker/corosync provides crm_feature_set 3.0.10?

[Vitaly Zolotusky]

Ulrich, 
Yes, Fedora is far ahead of 22, but our product was in the field for quite a few years. Later versions are running on 28, but now we are moved on to CentOs. 
Upgrade was always happening online with no service interruption.
The problem with upgrade to the new version of Corosync is that it does not talk to the old one.
Now that we need to replace Pacemaker, Corosync and Postgres we need to have one brief interruption for Pacemaker, Corosync and Postgres update, but before we update Pacemaker we have to sync new nodes with old ones to keep cluster running until all nodes are ready. 
So what we do is - we install new nodes with old version of Pacemaker, Corosync and Postgres, have them running in mixed (old/new) configuration until all are ready for new Pacemaker, Corosync and Postgres and then we shutdown the cluster for couple of min and upgrade Pacemaker, Corosync and Postgres. 
The only reason we shutdown the cluster now is because old Corosync does not talk to new Corosync.
_Vitaly

> On November 24, 2021 2:22 AM Ulrich Windl <ulrich.windl at rz.uni-regensburg.de> wrote:
> 
>  
> >>> vitaly <vitaly at unitc.com> schrieb am 23.11.2021 um 20:11 in Nachricht
> <45677632.67420.1637694706150 at webmail6.networksolutionsemail.com>:
> > Hello,
> > I am working on the upgrade from older version of pacemaker/corosync to the
> 
> > current one. In the interim we need to sync newly installed node with the 
> > node running old software. Our old node uses pacemaker 1.1.13‑3.fc22 and 
> > corosync 2.3.5‑1.fc22 and has crm_feature_set 3.0.10.
> > 
> > For interim sync I used pacemaker 1.1.18‑2.fc28 and corosync 2.4.4‑1.fc28. 
> > This version is using crm_feature_set 3.0.14. 
> > This version is working fine, but it has issues in some edge cases, like 
> > when the new node starts alone and then the old one tries to join.
> 
> What I'm wondering (not wearing a red hat): Isn't Fedora at something like 33
> or 34 right now?
> If so, why bother with such old versions?
> 
> > 
> > So I need to rebuild rpms for crm_feature_set 3.0.10. This will be used just
> 
> > once and then it will be upgraded to the latest versions of pacemaker and 
> > corosync.
> > 
> > Now, couple of questions:
> > 1. Which rpm defines crm_feature_set?
> > 2. Which version of this rpm has crm_feature_set 3.0.10?
> > 3. Where could I get source rpms to rebuild this rpm on CentOs 8?
> > Thanks a lot!
> > _Vitaly Zolotusky
> > _______________________________________________
> > Manage your subscription:
> > https://lists.clusterlabs.org/mailman/listinfo/users 
> > 
> > ClusterLabs home: https://www.clusterlabs.org/