[Pacemaker] ocf:heartbeat:pingd receives wrong value in $__ACTION

[Andrew Beekhof]

On Thu, Nov 19, 2009 at 3:34 PM, Dejan Muhamedagic <dejanmm at fastmail.fm> wrote:
> Hi,
>
> On Thu, Nov 19, 2009 at 01:17:10PM +0100, Andrew Beekhof wrote:
>> On Thu, Nov 19, 2009 at 12:30 PM, Dejan Muhamedagic <dejanmm at fastmail.fm> wrote:
>> > Hi,
>> >
>> > On Thu, Nov 19, 2009 at 09:05:18AM +0100, Andrew Beekhof wrote:
>> >> On Wed, Nov 18, 2009 at 11:04 PM, hj lee <kerdosa at gmail.com> wrote:
>> >> > Hi,
>> >> >
>> >> > Sorry for long delay. This is my pingd configuration.
>> >> >
>> >> > primitive pingd-res ocf:heartbeat:pingd \
>> >> >         params dampen="5s" multiplixer="20000" host_list="my-gateway-ip" \
>> >> >         op pingd-monitor-op interval="1s" timeout="10s" \
>> >>
>> >> this is your problem.  you should have this instead:
>> >>    op monitor interval="1s" timeout="10s"
>> >
>> > crm will now check if the operation name really makes sense.
>>
>> This is only a warning though right?
>
> No, it would be an error. Why's that a problem?

Because OCF only specifies which actions an RA must support, it is
allowed to support more.

> BTW, the list of allowed
> operations is:
>
> ["monitor", "start", "stop", "migrate_to", "migrate_from"]

Well for a start you forgot demote and promote.
We're also planning freeze,thaw, and backup.

Seriously, do not make this an error.