[Pacemaker] crm_master triggering assert section != NULL

[Yves Trudeau]

Hi,
    following my previous post to the wrong list, forwarded to the 
Pacemaker list by Florian, here is the my complete cluster configuration:

http://pastebin.com/zDj0MF1Z

Just to recall the original message:

     I started to have issues with crm_master with Pacemaker 1.0.11.  I
think I traced it down to the following problem.  I know crm_master is
supposed to be called within the resource script, calling manually helps
to illustrate the problem.

root at testvirtbox1:~# /usr/sbin/crm_master -l reboot -v 1000 -r
p_MySQL_replication:0
root at testvirtbox1:~# /usr/local/sbin/crm_master -r
'p_MySQL_Replication:0' -G
    name=master-p_MySQL_Replication:0 value=(null)
Error performing operation: cib object missing

and in daemon.log:

Oct 11 12:17:41 testvirtbox1 crm_attribute: [21986]: info: Invoked:
crm_attribute -N testvirtbox1 -n master-p_MySQL_Replication:0 -G
Oct 11 12:17:41 testvirtbox1 crm_attribute: [21986]: ERROR: crm_abort:
read_attr: Triggered assert at cib_attrs.c:297 : section != NULL


while in cid I found this part:

<transient_attributes id="testvirtbox1">
<instance_attributes id="status-testvirtbox1">
<nvpair id="status-testvirtbox1-probe_complete" name="probe_complete"
value="true"/>
<nvpair id="status-testvirtbox1-master-p_MySQL_replication:0"
name="master-p_MySQL_replication:0" value="1000"/>
</instance_attributes>
</transient_attributes>

Is this a problem with my CIB or a bug in crm_attribute?  Until
recently,  I pretty sure this was working correctly, I don't know what
triggered the problem.   crm_verify -L -V returns nothing.



Regards,

Yves