On Wed, Dec 7, 2011 at 9:49 AM, Florian Haas <flor...@hastexo.com> wrote: > On Tue, Dec 6, 2011 at 3:47 PM, Bensch, Kobus > <kobus.ben...@bauerservices.co.uk> wrote: >> 2.) I pasted the outcome here http://pastebin.com/uPcHiM4p > > So, you should be seeing lines akin to the following in your logs: > > ERROR: clone_rsc_colocation_rh: Cannot interleave clone ActiveFTPSite > and WebIP because they do not support the same number of resources per > node > ERROR: clone_rsc_colocation_rh: Cannot interleave clone ActiveFTPSite > and WebIP because they do not support the same number of resources per > node > > Andrew: this configuration appears to come from CFS > (http://www.clusterlabs.org/doc/en-US/Pacemaker/1.1/html/Clusters_from_Scratch/ch08s06.html); > that documentation seems like it needs to be updated. Either one would > need to disable interleaving (which is now enabled by default, iirc), > or set clone-node-max=”1” on the IPaddr2 clone.
I will likely give that document a major overhaul for fedora 17. I wonder if the IPaddr2 clone will behave correctly with clone-node-max=”1” (ie. do the number of buckets get reduced when its stopped on a node) > > Interestingly, in 1.1.5, setting interleave=false on both clones in > the given CIB does _not_ seem to fix the problem (ptest still > complains about "cannot interleave"), only setting clone-node-max=1 on > the IPaddr2 clone does. Am I doing something wrong, or does this look > like a pengine bug? Sounds like a bug. Could someone create a bugzilla for that please? _______________________________________________ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
