[Pacemaker] [Linux-HA] OCF_RESKEY_CRM_meta_timeout not matching monitor timeout meta-data

[Brett Delle Grazie]

Hi,

Apologies for reposting, but I forgot to 'reply-all'. Details below.

On 14 February 2011 09:04, Andrew Beekhof <andrew at beekhof.net> wrote:
> On Fri, Feb 4, 2011 at 11:23 AM, Brett Delle Grazie
> <brett.dellegrazie at gmail.com> wrote:
>> Hi,
>>
>> Apologies for cross-posting but I'm not sure where this problem resides.
>>
>> I'm running:
>> corosync-1.2.7-1.1.el5.x86_64
>> corosynclib-1.2.7-1.1.el5.x86_64
>> cluster-glue-1.0.6-1.6.el5.x86_64
>> cluster-glue-libs-1.0.6-1.6.el5.x86_64
>> pacemaker-1.0.10-1.4.el5.x86_64
>> pacemaker-libs-1.0.10-1.4.el5.x86_64
>> resource-agents-1.0.3-2.6.el5.x86_64
>>
>> on RHEL5.
>>
>> In one of my resource agents (tomcat) I'm directly outputting the result of:
>> $((OCF_RESKEY_CRM_meta_timeout/1000))
>> to an external file.
>> and its coming up with a value of '100'
>>
>> Whereas the resource definition in pacemaker specifies timeout of '30'
>> specifically:
>>
>> primitive tomcat_tc1 ocf:intact:tomcat \
>>        params tomcat_user="tomcat" catalina_home="/opt/tomcat6"
>> catalina_pid="/home/tomcat/tc1/temp/tomcat.pid"
>> catalina_rotate_log="NO" script_log="/home/tomcat/tc1/logs/tc1.log"
>> statusurl="http://127.0.0.1/version/" java_home="/usr/lib/jvm/java" \
>>        op start interval="0" timeout="70" \
>>        op stop interval="0" timeout="20" \
>>        op monitor interval="60" timeout="30" start-delay="70"
>>
>> Is this a known bug?
>
> No.  Could you file a bug please?

Bug filed: http://developerbugs.linux-foundation.org/show_bug.cgi?id=2560

>
>> Does it affect all operation timeouts?
>
> Unknown
>
Okay thanks.

-- 
Best Regards,

Brett Delle Grazie