Re: [Pacemaker] When pacemaker expects resource to go directly to Master after start?

2014-10-05 Thread Andrew Beekhof
On 2 Oct 2014, at 8:02 pm, Andrei Borzenkov wrote: > According to documentation (Pacemaker 1.1.x explained) "when > [Master/Slave] the resource is started, it must come up in the > mode called Slave". But what I observe here - in some cases pacemaker > treats Slave state as error. As example (pa

Re: [Pacemaker] When pacemaker expects resource to go directly to Master after start?

2014-10-02 Thread Andrei Borzenkov
On Thu, Oct 2, 2014 at 2:36 PM, emmanuel segura wrote: > I don't know if you can use Dummy primitivi as MS > > egrep "promote|demote" /usr/lib/ocf/resource.d/pacemaker/Dummy > echo $? > 1 > Yes, I know I'm not bright, but still not *that* stupid :) cn1:/usr/lib/ocf/resource.d # grep -E 'promote|

Re: [Pacemaker] When pacemaker expects resource to go directly to Master after start?

2014-10-02 Thread emmanuel segura
I don't know if you can use Dummy primitivi as MS egrep "promote|demote" /usr/lib/ocf/resource.d/pacemaker/Dummy echo $? 1 2014-10-02 12:02 GMT+02:00 Andrei Borzenkov : > According to documentation (Pacemaker 1.1.x explained) "when > [Master/Slave] the resource is started, it must come up in t

[Pacemaker] When pacemaker expects resource to go directly to Master after start?

2014-10-02 Thread Andrei Borzenkov
According to documentation (Pacemaker 1.1.x explained) "when [Master/Slave] the resource is started, it must come up in the mode called Slave". But what I observe here - in some cases pacemaker treats Slave state as error. As example (pacemaker 1.1.9): Oct 2 13:23:34 cn1 pengine[9446]: notice: