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

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

Re: [ClusterLabs] Upgrading/downgrading cluster configuration

> On October 22, 2020 1:54 PM Strahil Nikolov wrote: > > > Have you tried to backup the config via crmsh/pcs and when you downgrade to > restore from it ? > > Best Regards, > Strahil Nikolov > > > > > > > В четвъртък, 22 октомври 2020 г., 15

[ClusterLabs] Upgrading/downgrading cluster configuration

Hello, We are trying to upgrade our product from Corosync 2.X to Corosync 3.X. Our procedure includes upgrade where we stopthe cluster, replace rpms and restart the cluster. Upgrade works fine, but we also need to implement rollback in case something goes wrong. When we rollback and reload old

Re: [ClusterLabs] Antw: [EXT] Rolling upgrade from Corosync 2.3+ to Corosync 2.99+ or Corosync 3.0+?

umber and a > request to use a different version number would be needed, too. > > Regards, > Ulrich > > >>> Vitaly Zolotusky schrieb am 11.06.2020 um 04:14 in > Nachricht > <19881_1591841678_5EE1938D_19881_553_1_1163034878.247559.1591841668387@webmail6. >

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

trahil Nikolov > > На 11 юни 2020 г. 17:48:47 GMT+03:00, Vitaly Zolotusky > написа: > >Thank you very much for quick reply! > >I will try to either build new version on Fedora 22, or build the old > >version on CentOs 8 and do a HA stack upgrade separately from my full

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

Thank you very much for quick reply! I will try to either build new version on Fedora 22, or build the old version on CentOs 8 and do a HA stack upgrade separately from my full product/OS upgrade. A lot of my customers would be extremely unhappy with even short downtime, so I can't really do

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

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

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

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: 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

Re: [ClusterLabs] Fence_sbd script in Fedora30?

have is that we modify scripts to work with our hardware and I am in the process of going through these changes. Thanks again! _Vitaly > On September 24, 2019 at 12:29 AM Andrei Borzenkov > wrote: > > > 23.09.2019 23:23, Vitaly Zolotusky пишет: > > Hello, > > I am try

[ClusterLabs] Fence_sbd script in Fedora30?

Hello, I am trying to upgrade to Fedora 30. The platform is two node cluster with pacemaker. It Fedora 28 we were using old fence_sbd script from 2013: # This STONITH script drives the shared-storage stonith plugin. # Copyright (C) 2013 Lars Marowsky-Bree We were overwriting the

Re: [ClusterLabs] HA domain controller fences newly joined node after fence_ipmilan delay even if transition was aborted.

ich both nodes will start corosync/pacemaker > close in time. If one node never comes up, then it will wait 10 minutes > before starting, after which the other node will be fenced (startup fencing > and subsequent resource startup will only happen will only occur if > no-quorum-

Re: [ClusterLabs] Antw: HA domain controller fences newly joined node after fence_ipmilan delay even if transition was aborted.

an indication that something is not working right and we would like to get to the bottom of it. Thanks again! _Vitaly > On December 18, 2018 at 1:47 AM Ulrich Windl > wrote: > > > >>> Vitaly Zolotusky schrieb am 17.12.2018 um 21:43 in > >>> Nachr

Re: [ClusterLabs] HA domain controller fences newly joined node after fence_ipmilan delay even if transition was aborted.

e as close to each other as possible. Thanks again! _Vitaly > On December 17, 2018 at 6:01 PM Ken Gaillot wrote: > > > On Mon, 2018-12-17 at 15:43 -0500, Vitaly Zolotusky wrote: > > Hello, > > I have a 2 node cluster and stonith is configured for SBD and > > fen