[Pacemaker] ocf_is_probe() problem on debian

[Florian Haas]

Tom,

thanks:

http://hg.linux-ha.org/agents/rev/44b1ba8c7804

See http://developerbugs.linux-foundation.org/show_bug.cgi?id=2284 for
the discussion.

Cheers,
Florian

On 2010-02-15 12:46, Tom Weber wrote:
> Hello,
> 
> the setup:
> debian lenny based pacemaker cluster.
> these packages from http://people.debian.org/~madkiss/ha
> 
> cluster-agents     1:1.0.2-1~bpo50+1
> cluster-glue       1.0.3-1~bpo50+1
> pacemaker          1.0.7+hg20100203-1~bpo50+1
> libheartbeat2      1:3.0.2-1~bpo50+1
> corosync           1.2.0-1~bpo50+1
> libcorosync4       1.2.0-1~bpo50+1     
> 
> I'm using ocf::heartbeat:IPaddr2 and ocf::heartbeat:Route in a resource
> Group. The IPaddr2 defines the interface for which i want to set up the
> route.
> During startup of the resource Group, the probe of the Route Ressource
> fails with OCF_ERR_INSTALLED.
> 
> Digging into the shell scripts i found in
> /usr/lib/ocf/resource.d/heartbeat/.ocf-shellfuncs:
> ~line 355 
> 
> # returns true if the CRM is currently running a probe. A probe is
> # defined as a monitor operation with a monitoring interval of zero.
> ocf_is_probe() {
>     [ "$__OCF_ACTION" = "monitor" -a "$OCF_RESKEY_CRM_meta_interval" = 0 ]
> }
> 
> The problem seems to be that during a probe OCF_RESKEY_CRM_meta_interval
> is not set at all / empty, so ocf_is_probe() always fails.
> 
> According to the comment in the source something seems to not setup the
> environment correctly. Maybe it's just combination of packages in the
> repository.
> 
> As this is my first contact with pacemaker I've got plenty other
> interesting stuff to learn, so i first uglyfixed this by adding 
> test -z "$OCF_RESKEY_CRM_meta_interval" && OCF_RESKEY_CRM_meta_interval=0
> to the Route agent. Later on another agent failed with the same problem,
> so i moved this into ocf_is_probe() - which is for sure not the correct
> way and place to fix this.
> 
>   Tom

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 260 bytes
Desc: OpenPGP digital signature
URL: <https://lists.clusterlabs.org/pipermail/pacemaker/attachments/20100215/d2c45e04/attachment-0004.sig>