Old pcs-0.9.167/0.9.168/0.9.169 package with newer corosync-3.1 and pacemaker-2.1 on RHEL 7.7

List overview All Threads
Download

newer

older

kronosnet v1.21 released

kronosnet v1.20 released

RUGINA Szabolcs-Gavril

5 Feb 2021 5 Feb '21

9:17 a.m.

Hi folks, Thank you for your time and will to help. We are in the middle of a high pressure because some problems with RHEL HA Cluster/Corosync+Pacemaker/DRBD and we arrived at the point that we upgraded corosync 2.4.3 to 3.1 and pacemaker 1.1.20 to 2.1 but then our setup gives errors with the command "pcs property set no-quorum-policy=stop". The error is: No such file or directory', 'command': '/usr/libexec/pacemaker/pengine metadata' Indeed /usr/libexec/pacemaker/pengine does not exists, I assume it is OK, because in the new pacemaker 3.1 the internal structure was changed.. In the midtime we found out that we could archive the same setting using crm_attribute --name no-quorum-policy -update stop. My questions are: * Is there a reason that pcs has no build for RHEL 7? * Is the crm_attribute the right choice for setting cluster properties and will cover all usecases? * Thank You! BR, Szabolcs

Attachments:

attachment.html (text/html — 6.4 KB)

Show replies by date

Fabio M. Di Nitto

8 Feb 8 Feb

7:42 a.m.

Hi, adding the lead developer for pcs, and the pacemaker user devel mailing list. This mailing list is specific to kronosnet development. On 05/02/2021 10.17, RUGINA Szabolcs-Gavril wrote:

...

Hi folks, Thank you for your time and will to help. We are in the middle of a high pressure because some problems with RHEL HA Cluster/Corosync+Pacemaker/DRBD and we arrived at the point that we upgraded corosync 2.4.3 to 3.1 and pacemaker 1.1.20 to 2.1 but then our setup gives errors with the command “pcs property set no-quorum-policy=stop”. The error is: /No such file or directory', 'command': '/usr/libexec/pacemaker/pengine metadata’/ Indeed //usr/libexec/pacemaker/pengine /does not exists, I assume it is OK, because in the new pacemaker 3.1 the internal structure was changed.. In the midtime we found out that we could archive the same setting using crm_attribute --name no-quorum-policy –update stop. My questions are: * Is there a reason that pcs has no build for RHEL 7?

I can only answer this question, newer version of pcs needs ruby and python in versions that are not supported on RHEL7 and even if we can build the package, it won´t run. Fabio

...

* Is the crm_attribute the right choice for setting cluster properties and will cover all usecases? * Thank You! BR, Szabolcs _______________________________________________ Users mailing list Users(a)lists.kronosnet.org https://lists.kronosnet.org/mailman/listinfo/users

RUGINA Szabolcs-Gavril

7:54 a.m.

Hi Fabio, Thank You for your answer! BR, Szabi. _______________________________________________________ Szabolcs-Gavril Rugina Development Information Technologies 1 / Software Engineer FREQUENTIS ROMÂNIA SRL Str. Taietura Turcului, Nr. 47, 400221, Cluj-Napoca, Romania Phone +43-1-81150-7511 Mobile +40-771-483274 Web http://www.frequentis.ro E-Mail szabolcs.rugina(a)frequentis.com Nr. O.R.C./an: J12/957/2009 CUI: RO 25475641 _______________________________________________________ -----Original Message----- From: Fabio M. Di Nitto <fabbione(a)fabbione.net> Sent: Monday, February 8, 2021 9:43 AM To: RUGINA Szabolcs-Gavril <Szabolcs.RUGINA(a)frequentis.com>om>; users(a)lists.kronosnet.org; Tomas Jelinek <tojeline(a)redhat.com>om>; users(a)clusterlabs.org Subject: Re: Old pcs-0.9.167/0.9.168/0.9.169 package with newer corosync-3.1 and pacemaker-2.1 on RHEL 7.7 Hi, adding the lead developer for pcs, and the pacemaker user devel mailing list. This mailing list is specific to kronosnet development. On 05/02/2021 10.17, RUGINA Szabolcs-Gavril wrote:

...

Hi folks, Thank you for your time and will to help. We are in the middle of a high pressure because some problems with RHEL HA Cluster/Corosync+Pacemaker/DRBD and we arrived at the point that we upgraded corosync 2.4.3 to 3.1 and pacemaker 1.1.20 to 2.1 but then our setup gives errors with the command "pcs property set no-quorum-policy=stop". The error is: /No such file or directory', 'command': '/usr/libexec/pacemaker/pengine metadata'/ Indeed //usr/libexec/pacemaker/pengine /does not exists, I assume it is OK, because in the new pacemaker 3.1 the internal structure was changed.. In the midtime we found out that we could archive the same setting using crm_attribute --name no-quorum-policy -update stop. My questions are: * Is there a reason that pcs has no build for RHEL 7?

I can only answer this question, newer version of pcs needs ruby and python in versions that are not supported on RHEL7 and even if we can build the package, it won´t run. Fabio

...

Tomas Jelinek

9:21 a.m.

Hi, There are significant changes between corosync 2.x and 3.x and similarly between pacemaker 1.x and 2.x. To cover those and support the new versions, we created pcs-0.10 branch. The old versions are supported by pcs-0.9 branch. RHEL 7 ships corosync 2.x and pacemaker 1.x, so we build pcs-0.9.x for it. Corosync 3.x and pacemaker 2.x are shipped in RHEL 8, so that's where pcs-0.10 goes. RHEL 8 also ships new version of ruby and python. So on top of modifications needed for corosync 3.x and pacemaker 2.x support, we used the opportunity to get rid of legacy code supporting those end-of-life python and ruby versions. Regards, Tomas Dne 08. 02. 21 v 8:42 Fabio M. Di Nitto napsal(a):

...

Hi, adding the lead developer for pcs, and the pacemaker user devel mailing list. This mailing list is specific to kronosnet development. On 05/02/2021 10.17, RUGINA Szabolcs-Gavril wrote:

Hi folks, Thank you for your time and will to help. We are in the middle of a high pressure because some problems with RHEL HA Cluster/Corosync+Pacemaker/DRBD and we arrived at the point that we upgraded corosync 2.4.3 to 3.1 and pacemaker 1.1.20 to 2.1 but then our setup gives errors with the command “pcs property set no-quorum-policy=stop”. The error is: /No such file or directory', 'command': '/usr/libexec/pacemaker/pengine metadata’/ Indeed //usr/libexec/pacemaker/pengine /does not exists, I assume it is OK, because in the new pacemaker 3.1 the internal structure was changed.. In the midtime we found out that we could archive the same setting using crm_attribute --name no-quorum-policy –update stop. My questions are: * Is there a reason that pcs has no build for RHEL 7?

I can only answer this question, newer version of pcs needs ruby and python in versions that are not supported on RHEL7 and even if we can build the package, it won´t run. Fabio

Ken Gaillot

3:52 p.m.

New subject: [ClusterLabs] Old pcs-0.9.167/0.9.168/0.9.169 package with newer corosync-3.1 and pacemaker-2.1 on RHEL 7.7

Due to the concerns already mentioned, it is much easier to stick with Corosync 2 + Pacemaker 1 on RHEL 7, but I will mention that the particular issue in the original message should be resolved if Pacemaker 2 is built with ./configure --enable-legacy-links. However pcs 0.9 would still only be partially usable. On Mon, 2021-02-08 at 10:21 +0100, Tomas Jelinek wrote:

...

Hi, There are significant changes between corosync 2.x and 3.x and similarly between pacemaker 1.x and 2.x. To cover those and support the new versions, we created pcs-0.10 branch. The old versions are supported by pcs-0.9 branch. RHEL 7 ships corosync 2.x and pacemaker 1.x, so we build pcs-0.9.x for it. Corosync 3.x and pacemaker 2.x are shipped in RHEL 8, so that's where pcs-0.10 goes. RHEL 8 also ships new version of ruby and python. So on top of modifications needed for corosync 3.x and pacemaker 2.x support, we used the opportunity to get rid of legacy code supporting those end-of- life python and ruby versions. Regards, Tomas Dne 08. 02. 21 v 8:42 Fabio M. Di Nitto napsal(a):

Hi, adding the lead developer for pcs, and the pacemaker user devel mailing list. This mailing list is specific to kronosnet development. On 05/02/2021 10.17, RUGINA Szabolcs-Gavril wrote:

Hi folks, Thank you for your time and will to help. We are in the middle of a high pressure because some problems with RHEL HA Cluster/Corosync+Pacemaker/DRBD and we arrived at the point that we upgraded corosync 2.4.3 to 3.1 and pacemaker 1.1.20 to 2.1 but then our setup gives errors with the command “pcs property set no-quorum-policy=stop”. The error is: /No such file or directory', 'command': '/usr/libexec/pacemaker/pengine metadata’/ Indeed //usr/libexec/pacemaker/pengine /does not exists, I assume it is OK, because in the new pacemaker 3.1 the internal structure was changed.. In the midtime we found out that we could archive the same setting using crm_attribute --name no-quorum-policy –update stop. My questions are: * Is there a reason that pcs has no build for RHEL 7?

I can only answer this question, newer version of pcs needs ruby and python in versions that are not supported on RHEL7 and even if we can build the package, it won´t run. Fabio > * Is the crm_attribute the right choice for setting cluster > properties > and will cover all usecases? > * > > Thank You! > > BR, > > Szabolcs > > > _______________________________________________ > Users mailing list > Users(a)lists.kronosnet.org > https://lists.kronosnet.org/mailman/listinfo/users >

_______________________________________________ Manage your subscription: https://lists.clusterlabs.org/mailman/listinfo/users ClusterLabs home: https://www.clusterlabs.org/

-- Ken Gaillot <kgaillot(a)redhat.com>

1412

days inactive

1415

days old

users@lists.kronosnet.org

Manage subscription

4 comments

4 participants

tags (0)

participants (4)

Fabio M. Di Nitto
Ken Gaillot
RUGINA Szabolcs-Gavril
Tomas Jelinek