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.rug...@frequentis.com Nr. O.R.C./an: J12/957/2009 CUI: RO 25475641 _______________________________________________________ -----Original Message----- From: Fabio M. Di Nitto <fabbi...@fabbione.net> Sent: Monday, February 8, 2021 9:43 AM To: RUGINA Szabolcs-Gavril <szabolcs.rug...@frequentis.com>; us...@lists.kronosnet.org; Tomas Jelinek <tojel...@redhat.com>; users@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 > * Is the crm_attribute the right choice for setting cluster properties > and will cover all usecases? > * > > Thank You! > > BR, > > Szabolcs > > > _______________________________________________ > Users mailing list > us...@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/
