On Fri, May 28, 2010 at 8:00 AM, Andrew Beekhof wrote:
>
> > I don't know if it is the same bug...
> > In the sense that in your bug case the problem is related to:
> > - the stop operation not enforcing the order constraint
> > - the constraint is between a clone of a group and a clone of a reso
On Thu, May 27, 2010 at 6:41 PM, Gianluca Cecchi
wrote:
> On Tue, May 25, 2010 at 3:39 PM, Dejan Muhamedagic
> wrote:
>>
>> Hi,
>> [snip]
>> > So I presume the problem could be caused by the fact that the second
>> > part is
>> > a clone and not a resource? or a bug?
>> > I can eventually send th
On Tue, May 25, 2010 at 3:39 PM, Dejan Muhamedagic wrote:
> Hi,
>
> On Thu, May 20, 2010 at 06:09:01PM +0200, Gianluca Cecchi wrote:
>> Hello,
>> manual for 1.0 (and 1.1) reports this for Advisory Ordering:
>>
>> On the other-hand, when score="0" is specified for a constraint, the
>> constraint is
On Tue, May 25, 2010 at 3:39 PM, Dejan Muhamedagic wrote:
> Hi,
> [snip]
> > So I presume the problem could be caused by the fact that the second part
> is
> > a clone and not a resource? or a bug?
> > I can eventually send the whole config.
>
> Looks like a bug to me. Clone or resource, constrain
Hi,
On Thu, May 20, 2010 at 06:09:01PM +0200, Gianluca Cecchi wrote:
> Hello,
> manual for 1.0 (and 1.1) reports this for Advisory Ordering:
>
> On the other-hand, when score="0" is specified for a constraint, the
> constraint is considered optional and only has an effect when both resources
> ar
Hello,
manual for 1.0 (and 1.1) reports this for Advisory Ordering:
On the other-hand, when score="0" is specified for a constraint, the
constraint is considered optional and only has an effect when both resources
are stopping and or starting. Any change in state by the first resource will
have no
