On Jan 4, 2008, at 3:52 PM, Thomas Glanzmann wrote:
Hello Andrew,
It means the transition graph we produced wasn't completely sane (ie.
there was a bug).
Earlier on the logs would have mentioned which PE input file the
graph
was based on... if you find that and attach it, i'll make sure it
gets
fixed.
Dominik found the problem. See the other thread. The problem was I had
two monitor operations for a Master/Slave resource with the same
interval.
The bug triggers with:
<master_slave id="ms-drbd0">
<meta_attributes id="ma-ms-drbd0">
<attributes>
<nvpair id="ma-ms-drbd0-1"
name="clone_max" value="2"/>
<nvpair id="ma-ms-drbd0-2"
name="clone_node_max" value="1"/>
<nvpair id="ma-ms-drbd0-3"
name="master_max" value="1"/>
<nvpair id="ma-ms-drbd0-4"
name="master_node_max" value="1"/>
<nvpair id="ma-ms-drbd0-5"
name="notify" value="yes"/>
<nvpair id="ma-ms-drbd0-6"
name="globally_unique" value="false"/>
</attributes>
</meta_attributes>
<primitive id="drbd0" class="ocf"
provider="heartbeat" type="drbd">
<instance_attributes id="ia-drbd0">
<attributes>
<nvpair id="ia-
drbd0-1" name="drbd_resource" value="postgres"/>
</attributes>
</instance_attributes>
<operations>
<op id="op-ms-drbd2-1"
name="monitor" interval="60s" timeout="60s" start_delay="30s"
role="Master"/>
<op id="op-ms-drbd2-2"
name="monitor" interval="60s" timeout="60s" start_delay="30s"
role="Slave"/>
</operations>
</primitive>
</master_slave>
And it doesn't trigger if someone sets the interval of the two monitor
operations to different intervals.
I reproduced the problem for you and attached the requested file.
Thanks - the PE is now smart enough to at least filter out the
duplicates :-)
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
