It appears that when creating a clone as the second resource in an order rule, the rule is ignored when deciding when to start the clone.
I'm using Pacemaker 1.0.9.1 - I've cut it down to the following simple example, but it seems to happen no matter what resource agents are involved: property stonith-enabled=false rsc_defaults resource-stickiness=20 primitive smb_lsb lsb:smb primitive cups_lsb lsb:cups clone cups_clone cups_lsb meta clone-max="2" clone-node-max="1" globally-unique="false" order smb_lsb-before-cups_clone inf: smb_lsb:start cups_clone:start The cups_clone and smb_lsb resources all start at the same time, without the order rule appearing to be processed. The dot graph from this config is here: http://imagebin.ca/view/q8ihn80u.html If I remove the clone line and make the order depend on a simple primitive resource, all works as expected. Any ideas? Matthew -- The University of Edinburgh is a charitable body, registered in Scotland, with registration number SC005336.
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
