Re: [ClusterLabs] pacemaker 2.0.5 version pcs status resources command is not working

With that in mind, I'd suggest upgrading to a newer pcs version if possible. If not, then you may have to do something more hack-y, like `pcs status | grep '(.*:.*):'`. On Wed, Feb 3, 2021 at 1:26 PM Reid Wahl wrote: > Looks like pcs-0.9 isn't fully compatible with pacemaker >= 2.0.3. > - >

Re: [ClusterLabs] pacemaker 2.0.5 version pcs status resources command is not working

Looks like pcs-0.9 isn't fully compatible with pacemaker >= 2.0.3. - https://github.com/ClusterLabs/pcs/commit/0cf06b79f6dcabb780ee1fa7fee0565d73789329 The resource_status() function in older pcs versions doesn't match the lines in the crm_mon output of newer pacemaker versions. On Wed, Feb 3,

[ClusterLabs] pacemaker 2.0.5 version pcs status resources command is not working

Hi Team, In latest pacemaker version 2.0.5 we are not getting "pcs status resource" command output but in older version we used to get the output. Kindly let us know any already command to get pcs full list resource. Latest Pacemaker version : pacemaker-2.0.5 -->

[ClusterLabs] Antw: [EXT] Re: start vs promote drbd m/s colocation constraint

>>> Ken Gaillot schrieb am 03.02.2021 um 00:02 in Nachricht <396cc52f2d27b8aab611d2312ba172b07bdc9d7f.ca...@redhat.com>: > On Tue, 2021‑02‑02 at 14:27 ‑0700, Brent Jensen wrote: >> I've been trying to get my DRBD cluster on Centos8 / Pacemaker 2 to >> work but have had issues with cluster not

Re: [ClusterLabs] Antw: [EXT] pcs status command output consist of * in each line , is this expected behavior

On Wed, Feb 3, 2021 at 1:50 AM Ulrich Windl < ulrich.wi...@rz.uni-regensburg.de> wrote: > >>> S Sathish S schrieb am 02.02.2021 um 07:20 > in > Nachricht > < > dbbpr07mb73888356f8692d07d195ffb6d5...@dbbpr07mb7388.eurprd07.prod.outlook.com > > > > > Hi Team, > > > > we have taken latest pacemaker

[ClusterLabs] Antw: [EXT] pcs status command output consist of * in each line , is this expected behavior

>>> S Sathish S schrieb am 02.02.2021 um 07:20 in Nachricht > Hi Team, > > we have taken latest pacemaker version after that we found pcs status > command output consist of * in each line , is this expected behavior. > > https://github.com/ClusterLabs/pacemaker/tree/Pacemaker‑2.0.5 > > pcs

[ClusterLabs] Antw: [EXT] Anyone using remote-clear-port or remote-tls-port for remote CIB administration?

>>> Ken Gaillot schrieb am 02.02.2021 um 17:40 in Nachricht <5d7d52f14417e6e8baee49dfbc23884b5183b073.ca...@redhat.com>: > Hi all, > > Pacemaker has a feature allowing CIB modifications to be made from > hosts that are not cluster nodes: > >

[ClusterLabs] Q: Should a cleanup reset the failcount also?

Hi! I'm wondering: I had a failed clone resource. After fixing the problem, I performed a cleanup, but the fail-counts weren't reset (I thought that was the case in older versions of pacemaker): Before: Full List of Resources: * Clone Set: cln_iotw-md10 [prm_iotw-md10]: * Started: [ h19