please use hb_report and attach the tarball it creates to a new bugzilla entry.
On Tue, May 13, 2008 at 2:24 AM, Tim Serong <[EMAIL PROTECTED]> wrote: > Thomas Glanzmann wrote: > > > Tim, > > put them in a ressource group. A resource group, does, order colocation > > and stops all implictly. > > > > <group id="whatever"> > > ... > > </group> > > > > The resource group is what's not working. If the second resource in a > resource group can't start, the first one is stopped, then restarted, and > you end up with one resource running, one not. I've attached a CIB that > demonstrates this problem, along with a fake RA to simulate the resource > that can't start (put this in /usr/lib/ocf/resource.d/heartbeat). > > Here's what I've got, in summary: > > group-test-a (resource group) > group-test-a-res-1 (Dummy RA) > group-test-a-res-2 (Dummy-that-cant-start RA) > > group-test-b-res-1 (Dummy RA) > group-test-b-res-2 (Dummy-that-cant-start RA) > > > group-test-a ends up with group-test-a-res-1 started, group-test-a-res-2 > stopped. > > group-test-b-res-1 and group-test-b-res-2 are bound together with > colocation and ordering constraints and behave correctly, i.e. they both end > up stopped. > > Tim > > #!/bin/bash > > case $1 > in > start) > exit 1 > ;; > stop) > exit 0 > ;; > monitor) > exit 7 > ;; > *) > exit 1 > esac > > > _______________________________________________ > Linux-HA mailing list > [email protected] > http://lists.linux-ha.org/mailman/listinfo/linux-ha > See also: http://linux-ha.org/ReportingProblems > _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
