[Pacemaker] not able to configure operations(op) using pcs command

[Frank Brendel]

Hi Parveen,

my pacmaker version is 1.1.10 and pcs is 0.9.90 and it works as expected.

The bug you mentioned is fixed in pcs version 0.9.64.

pacemaker 1.1.8 is in RHEL 6.4 from February 2013. There is an update version 1.1.10 from November 2013.
Likely they fixed it already an you should update your os.



Regards
Frank

Am 23.01.2014 16:12, schrieb Parveen Jain:
Hi Frank.
Thanks for replying.
I did that, but it still gives the same output:

Following is the command and output:
pcs resource create app-prim ocf:appprim:appmmra-ra params appmm_health_check_port=65000 appmm_instance_name=appgw op monitor interval=1s timeout=5s start interval=0 timeout=60s stop interval=0 timeout=60s

pcs resource show app-prim
Resource: app-prim
  appmm_health_check_port: 65000
  appmm_instance_name: DESapigw
  op monitor interval=0 timeout=60s

I am just doubting, is this can be some issue with release of pacemaker I am using.
On googling, Found this issue: https://bugzilla.redhat.com/show_bug.cgi?id=912496
What I am using is 1.1.8-7.el6-394e906.
Anyone, from pacemaker developer if can comment on this(I am not sure on which version it is fixed).

Also One more issue I found was:
If I use following command(keeping my "start op" as first operation)
pcs resource create app-prim ocf:appprim:appmmra-ra params appmm_health_check_port=65000 appmm_instance_name=appgw op start interval=0 timeout=60s monitor interval=1s timeout=5s

I get following error in logs:
error: RecurringOp: Invalid recurring action app-prim-timeout-5s wth name: 'start'

Can anyone point out what can be the issue with this one too. Is it not accepting my "0" as my recurring value for "start" ?

Regards,
Parveen Jain

________________________________
From: Frank.Brendel at eurolog.com<mailto:Frank.Brendel at eurolog.com>
To: pacemaker at oss.clusterlabs.org<mailto:pacemaker at oss.clusterlabs.org>
Date: Thu, 23 Jan 2014 13:20:03 +0000
Subject: Re: [Pacemaker] not able to configure operations(op) using pcs command

Hi Parveen,

specify 'op' only once.

pcs resource create app-prim ocf:appprim:appmmra apigw_health_check_port=55000 appmm_instance_name=appgw op stop interval=0 timeout=60s monitor interval=1s timeout=5s start interval=0 timeout=60s


see 'pcs resource help'

create <resource id> <standard:provider:type|type> [resource options]
           [op <operation action> <operation options> [<operation action>
           <operation options>]...] [meta <meta options>...]
           [--clone <clone options> | --master <master options> |
           --group <group name>]



Regards
Frank


Am 23.01.2014 14:05, schrieb Parveen Jain:
Hi All,
  I am new to pacemaker and trying to port some of the CRM commands to PCS(for RHEL6.4). Getting following issue:

original command:


primitive app-prim ocf:appprim:appmm-ra \

        params appmm_health_check_port="55000" appmm_instance_name="INSTANCE_NAME" \

        op start interval="0" timeout="60s" \

        op stop interval="0" timeout="60s" \

        op monitor interval="1s" timeout="5s"


to following PCs command:


pcs resource create app-prim_ocf:appprim:appmmra apigw_health_check_port=55000 appmm_instance_name=appgw op stop interval=0 timeout=60s op monitor interval=1s timeout=5s op start interval=0 timeout=60s


but somehow this converted command is not working.


The main issue is use of "op" parameter with pcs command.

only the first command i.e. "op stop interval=0 timeout=60s" is effective. rest of the operations(op) are not effective at all.


whenever I do "pcs resource show app-prim" , following is output:


Resource: app-prim

   appmm_health_check_port: 65000

   appmm_instance_name: appgw

  op monitor interval=0s timeout=60s


Can anyone please help ?


my version of pcs is - Version: 1.1.8-7.el6-394e906


on RHEL 6.4



Thanks in advance for any help.


-Parveen



_______________________________________________
Pacemaker mailing list: Pacemaker at oss.clusterlabs.org<mailto:Pacemaker at oss.clusterlabs.org>
http://oss.clusterlabs.org/mailman/listinfo/pacemaker

Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://bugs.clusterlabs.org




_______________________________________________ Pacemaker mailing list: Pacemaker at oss.clusterlabs.org<mailto:Pacemaker at oss.clusterlabs.org> http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org



_______________________________________________
Pacemaker mailing list: Pacemaker at oss.clusterlabs.org<mailto:Pacemaker at oss.clusterlabs.org>
http://oss.clusterlabs.org/mailman/listinfo/pacemaker

Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://bugs.clusterlabs.org



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.clusterlabs.org/pipermail/pacemaker/attachments/20140123/d641bed1/attachment-0003.html>