On Tue, Jan 5, 2010 at 1:41 AM, Thomas Guthmann <tguthm...@iseek.com.au> wrote: > Re, > >> So cloned groups are not fun and side effects are random :) I will do >> more tests without IPAddr2 which seems a bit fancy and dodgy. > > I've just tried to clone a group tom-TEST containing 2 simple primitives > (ocf:homemade:named and ocf:pacemaker:Dummy). The group runs fine but when I > ask pacemaker to clone it, 2 orphans appear (tom-TEST:2 and tom-TEST:3). > Then if I decide to cleanup one orphan, a cloned group is stopped and moved > to the one I've just cleaned up. It's maybe be the default behaviour but i > don't understand what an orphan is, why they appear and how to get rid of > them once they appeared. Did I miss the chapter in 'configuration explained' > ? > > Is there any considerations/constraints I should be aware of when we want to > clone groups ?
There was a problem involving probing clones that I fixed in December. You're almost certainly hitting it, especially with crm_resource -C Any chance you could download the latest tarball and try that? http://hg.clusterlabs.org/pacemaker/stable-1.0/archive/1aa7cf1450e4.tar.bz2 _______________________________________________ Pacemaker mailing list Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker
