[ClusterLabs] Pacemaker 2.1.6-rc1 now available

Hi all, The first release candidate for Pacemaker 2.1.6 is now available at: https://github.com/ClusterLabs/pacemaker/releases/tag/Pacemaker-2.1.6-rc1 Highlights include new features for managing node attributes, and easier use of resource descroptions. Utilization node attributes may now be

Re: [ClusterLabs] HA problem: No live migration when setting node on standby

On Mon, Apr 17, 2023 at 10:48 AM Philip Schiller wrote: > > Hello Andrei, > > you wrote: > > >>As a workaround you could add dummy clone resource colocated with and > >>ordered after your DRBD masters and order VM after this clone. > > Thanks for the idea. This looks like a good option to solve

Re: [ClusterLabs] VirtualDomain - node map - ?

On 17/04/2023 06:17, Andrei Borzenkov wrote: On 16.04.2023 16:29, lejeczek via Users wrote: On 16/04/2023 12:54, Andrei Borzenkov wrote: On 16.04.2023 13:40, lejeczek via Users wrote: Hi guys Some agents do employ that concept of node/host map which I do not see in any manual/docs

Re: [ClusterLabs] Help with tweaking an active/passive NFS cluster

Andrei Borzenkov wrote on 05/04/2023 08:36: > On Fri, Mar 31, 2023 at 12:42 AM Ronny Adsetts > wrote: >> >> Hi, >> >> I wonder if someone more familiar with the workings of pacemaker/corosync >> would be able to assist in solving an issue. >> >> I have a 3-node NFS cluster which exports several

Re: [ClusterLabs] VirtualDomain - node map - ?

On Mon, Apr 17, 2023 at 6:17 AM Andrei Borzenkov wrote: > On 16.04.2023 16:29, lejeczek via Users wrote: > > > > > > On 16/04/2023 12:54, Andrei Borzenkov wrote: > >> On 16.04.2023 13:40, lejeczek via Users wrote: > >>> Hi guys > >>> > >>> Some agents do employ that concept of node/host map

Re: [ClusterLabs] resource going to blocked status while we restart service via systemctl twice

On Mon, Apr 17, 2023 at 9:25 AM S Sathish S via Users wrote: > Hi Team, > > > > TEST_node1 resource going to blocked status while we restart service via > systemctl twice in less time/before completion of 1st systemctl command. > > In older pacemaker version 2.0.2 we don’t see this issue, only

[ClusterLabs] HA problem: No live migration when setting node on standby

Hello Andrei, you wrote: As a workaround you could add dummy clone resource colocated with and ordered after your DRBD masters and order VM after this clone. Thanks for the idea. This looks like a good option to solve my problem. I have also researched a little more and came up with an

[ClusterLabs] resource going to blocked status while we restart service via systemctl twice

Hi Team, TEST_node1 resource going to blocked status while we restart service via systemctl twice in less time/before completion of 1st systemctl command. In older pacemaker version 2.0.2 we don't see this issue, only observing this issue on latest pacemaker version 2.1.15. [root@node1 ~]# pcs