Re: [ClusterLabs] crmsh resource failcount does not appear to work

2018-01-01 Thread Andrei Borzenkov
02.01.2018 06:48, Ken Gaillot пишет: > On Wed, 2017-12-27 at 14:03 +0300, Andrei Borzenkov wrote: >> On Wed, Dec 27, 2017 at 11:40 AM, Kristoffer Grönlund >> wrote: >>> >>> Andrei Borzenkov writes: >>> As far as I can tell, pacemaker acts on

Re: [ClusterLabs] crmsh resource failcount does not appear to work

2018-01-01 Thread Ken Gaillot
On Wed, 2017-12-27 at 14:03 +0300, Andrei Borzenkov wrote: > On Wed, Dec 27, 2017 at 11:40 AM, Kristoffer Grönlund > wrote: > > > > Andrei Borzenkov writes: > > > > > As far as I can tell, pacemaker acts on failcount attributes > > > qualified > > >

Re: [ClusterLabs] crmsh resource failcount does not appear to work

2017-12-27 Thread Kristoffer Grönlund
Andrei Borzenkov writes: > As far as I can tell, pacemaker acts on failcount attributes qualified > by operation name, while crm sets/queries unqualified attribute; I do > not see any syntax to set fail-count for specific operation in crmsh. crmsh uses crm_attribute to get

Re: [ClusterLabs] crmsh resource failcount does not appear to work

2017-12-27 Thread Andrei Borzenkov
On Wed, Dec 27, 2017 at 11:40 AM, Kristoffer Grönlund wrote: > > Andrei Borzenkov writes: > > > As far as I can tell, pacemaker acts on failcount attributes qualified > > by operation name, while crm sets/queries unqualified attribute; I do > > not see

[ClusterLabs] crmsh resource failcount does not appear to work

2017-12-24 Thread Andrei Borzenkov
As far as I can tell, pacemaker acts on failcount attributes qualified by operation name, while crm sets/queries unqualified attribute; I do not see any syntax to set fail-count for specific operation in crmsh. ha1:~ # rpm -q crmsh crmsh-4.0.0+git.1511604050.816cb0f5-1.1.noarch ha1:~ # crm_mon