Re: [ClusterLabs] [Problem] In RHEL8.4beta, pgsql resource control fails.

On Wed, 28 Apr 2021 12:00:40 -0500 Ken Gaillot wrote: > On Wed, 2021-04-28 at 18:14 +0200, Jehan-Guillaume de Rorthais wrote: > > Hi all, > > > > It seems to me the concern raised by Ulrich hasn't been discussed: > > > > On Wed, 12 Apr 2021 Ulrich Windl wrote: > > > > > Personally I think

Re: [ClusterLabs] [Problem] In RHEL8.4beta, pgsql resource control fails.

On Wed, 2021-04-28 at 18:14 +0200, Jehan-Guillaume de Rorthais wrote: > Hi all, > > It seems to me the concern raised by Ulrich hasn't been discussed: > > On Wed, 12 Apr 2021 Ulrich Windl wrote: > > > Personally I think an RA calling crm_mon is inherently broken: Will > > it ever > > pass

Re: [ClusterLabs] [Problem] In RHEL8.4beta, pgsql resource control fails.

Hi all, It seems to me the concern raised by Ulrich hasn't been discussed: On Wed, 12 Apr 2021 Ulrich Windl wrote: > Personally I think an RA calling crm_mon is inherently broken: Will it ever > pass ocf-tester? Would it be possible to rely on the following command ? cibadmin --query

Re: [ClusterLabs] Stopping the last node with pcs

On 2021-04-28 10:10 a.m., Ken Gaillot wrote: > On Tue, 2021-04-27 at 23:23 -0400, Digimer wrote: >> Hi all, >> >> I noticed something odd. >> >> >> [root@an-a02n01 ~]# pcs cluster status >> Cluster Status: >> Cluster Summary: >>* Stack: corosync >>* Current DC: an-a02n01 (version

Re: [ClusterLabs] Stopping the last node with pcs

On 4/28/21 4:10 PM, Ken Gaillot wrote: On Tue, 2021-04-27 at 23:23 -0400, Digimer wrote: Hi all, I noticed something odd. [root@an-a02n01 ~]# pcs cluster status Cluster Status: Cluster Summary: * Stack: corosync * Current DC: an-a02n01 (version 2.0.4-6.el8_3.2-2deceaa3ae) -

Re: [ClusterLabs] VirtualDomain craziness

On Wed, 2021-04-28 at 13:40 +0200, Ulrich Windl wrote: > Hi! > > I just discovered a problem after re-locating the configuration file > of a running VirtualDomain: > Cluster wanted to restart VM v14 on h18 due to configuration change > (which is correct). > Stop went OK, start failed with error

Re: [ClusterLabs] Stopping the last node with pcs

On Tue, 2021-04-27 at 23:23 -0400, Digimer wrote: > Hi all, > > I noticed something odd. > > > [root@an-a02n01 ~]# pcs cluster status > Cluster Status: > Cluster Summary: >* Stack: corosync >* Current DC: an-a02n01 (version 2.0.4-6.el8_3.2-2deceaa3ae) - > partition with quorum >

[ClusterLabs] VirtualDomain craziness

Hi! I just discovered a problem after re-locating the configuration file of a running VirtualDomain: Cluster wanted to restart VM v14 on h18 due to configuration change (which is correct). Stop went OK, start failed with error "already running". !!?? Still the cluster insisted on "recovering"

[ClusterLabs] Antw: [EXT] Stopping the last node with pcs

>>> Digimer schrieb am 28.04.2021 um 05:23 in Nachricht <721bab92-5686-955e-02c8-66269104c...@alteeve.ca>: > Hi all, > > I noticed something odd. > > > [root@an-a02n01 ~]# pcs cluster status > Cluster Status: > Cluster Summary: >* Stack: corosync >* Current DC: an-a02n01

Re: [ClusterLabs] Autostart/Enabling of Pacemaker and corosync

Thanks for the clarifications guys! Il giorno mar 27 apr 2021 alle ore 18:24 Jehan-Guillaume de Rorthais < j...@dalibo.com> ha scritto: > On Mon, 26 Apr 2021 18:04:41 + (UTC) > Strahil Nikolov wrote: > > > I prefer that the stack is auto enabled. Imagine that you got a DB that > is > >

[ClusterLabs] kronosnet v1.21 released

All, We are pleased to announce the general availability of kronosnet v1.21 kronosnet (or knet for short) is the new underlying network protocol for Linux HA components (corosync), that features the ability to use multiple links between nodes, active/active and active/passive link failover