Re: [Pacemaker] bug: multi state and target-role=started results in promote

2009-10-15 Thread Andrew Beekhof
On Thu, Oct 15, 2009 at 10:47 AM, Lars Ellenberg wrote: > On Thu, Oct 15, 2009 at 10:08:59AM +0200, Andrew Beekhof wrote: >> Hmmm... looks like "Slave" does the right thing, but not "Started" > > In that case, I vote for a Documentation change only. > > for MS resources, > target-role=Started is e

Re: [Pacemaker] bug: multi state and target-role=started results in promote

2009-10-15 Thread Raoul Bhatia [IPAX]
On 10/15/2009 11:17 AM, Lars Ellenberg wrote: >>> In that case, I vote for a Documentation change only. >>> > > >>> > > for MS resources, >>> > > target-role=Started is equivalent to target-role=Master >>> > > target-role=Slave is possible for MS resources only, and does just that. >>> > > target-

Re: [Pacemaker] bug: multi state and target-role=started results in promote

2009-10-15 Thread Dominik Klein
> i thought that for multistate resources, Started == Slave. > am i mistaken? did this change some time ago? Afaik, that was only true for status display in crm_mon. But also, that was fixed quite a while ago. Regards Dominik ___ Pacemaker mailing list

Re: [Pacemaker] bug: multi state and target-role=started results in promote

2009-10-15 Thread Lars Ellenberg
On Thu, Oct 15, 2009 at 10:58:12AM +0200, Raoul Bhatia [IPAX] wrote: > On 10/15/2009 10:47 AM, Lars Ellenberg wrote: > >> Hmmm... looks like "Slave" does the right thing, but not "Started" > > > > In that case, I vote for a Documentation change only. > > > > for MS resources, > > target-role=Star

Re: [Pacemaker] bug: multi state and target-role=started results in promote

2009-10-15 Thread Raoul Bhatia [IPAX]
On 10/15/2009 10:47 AM, Lars Ellenberg wrote: >> Hmmm... looks like "Slave" does the right thing, but not "Started" > > In that case, I vote for a Documentation change only. > > for MS resources, > target-role=Started is equivalent to target-role=Master > target-role=Slave is possible for MS reso

Re: [Pacemaker] bug: multi state and target-role=started results in promote

2009-10-15 Thread Lars Ellenberg
On Thu, Oct 15, 2009 at 10:08:59AM +0200, Andrew Beekhof wrote: > On Wed, Oct 14, 2009 at 5:07 PM, Rasto Levrinc > wrote: > > On Wed, October 14, 2009 4:36 pm, Andrew Beekhof wrote: > >> On Wed, Oct 14, 2009 at 4:12 PM, Lars Ellenberg > >> wrote: > >> > >>> > >>> > >>> with below config, accordi

Re: [Pacemaker] bug: multi state and target-role=started results in promote

2009-10-15 Thread Andrew Beekhof
On Wed, Oct 14, 2009 at 5:07 PM, Rasto Levrinc wrote: > On Wed, October 14, 2009 4:36 pm, Andrew Beekhof wrote: >> On Wed, Oct 14, 2009 at 4:12 PM, Lars Ellenberg >> wrote: >> >>> >>> >>> with below config, according to documentation, ms_res_Stateful_1 should >>> only be started, not promoted. >>

Re: [Pacemaker] bug: multi state and target-role=started results in promote

2009-10-14 Thread Rasto Levrinc
On Wed, October 14, 2009 4:36 pm, Andrew Beekhof wrote: > On Wed, Oct 14, 2009 at 4:12 PM, Lars Ellenberg > wrote: > >> >> >> with below config, according to documentation, ms_res_Stateful_1 should >> only be started, not promoted. >> >> but it gets promoted nontheless. >> >> Config bug? >> Docume

Re: [Pacemaker] bug: multi state and target-role=started results in promote

2009-10-14 Thread Andrew Beekhof
On Wed, Oct 14, 2009 at 4:12 PM, Lars Ellenberg wrote: > > > with below config, > according to documentation, > ms_res_Stateful_1 should only be started, not promoted. > > but it gets promoted nontheless. > > Config bug? > Documentation bug? > Code bug? Latter. Could I trouble you for the xml (wi

[Pacemaker] bug: multi state and target-role=started results in promote

2009-10-14 Thread Lars Ellenberg
with below config, according to documentation, ms_res_Stateful_1 should only be started, not promoted. but it gets promoted nontheless. Config bug? Documentation bug? Code bug? node sles11-a node sles11-b primitive res_Stateful_1 ocf:pacemaker:Stateful ms ms_res_Stateful_1 res_Stateful_1 \