[Pacemaker] About "record-pending"

[Yan Gao]

Hi Andrew,
I set "record-pending" attribute in the start operation of a resource,
like the following:

<primitive class="ocf" id="primitive_dummy" provider="pacemaker"
type="Dummy">
        <operations id="primitive_dummy-operations">
          <op id="primitive_dummy-operations-op_start" interval="0"
name="start" record-pending="true" timeout="90"/>
        </operations>
        <meta_attributes id="primitive_dummy-meta_attributes">
          <nvpair id="primitive_dummy-meta_attributes-target-role"
name="target-role" value="stopped"/>
        </meta_attributes>
</primitive>

And even set it in op_defaults :

<op_defaults>
      <meta_attributes id="meta_attributes">
        <nvpair id="nvpair-e541c964-d6a5-4512-b1a7-5f59ba7471b1"
name="record-pending" value="true"/>
      </meta_attributes>
</op_defaults>


But when I start the resource, there's no change in  
<lrm_rsc_op id="primitive_dummy_start_0" .../>

(Does it mean the "op-status" should be "-1" when pending?)

It seems that the set cannot be found in the hash table.

te_actions.c:461
value = g_hash_table_lookup(action->params,
crm_meta_name(XML_OP_ATTR_PENDING));

Did I make any mistake? Really strange...

Regards,
-- 
Yan Gao
China R&D Software Engineer
ygao at novell.com

Novell, Inc.
SUSE® Linux Enterprise 10
Your Linux is ready
http://www.novell.com/linux