Re: [Pacemaker] DRBD promotion timeout after pacemaker stop on other node

2013-11-12 Thread Vladislav Bogdanov
12.11.2013 09:56, Vladislav Bogdanov wrote: ... > Ah, then in_ccm will be set to false only when corosync (2) is stopped > on a node, not when pacemaker is stopped? > > Thus, current drbd agent/fencing logic does not (well) support just stop > of pacemaker in my use-case, messaging layer should be

Re: [Pacemaker] DRBD promotion timeout after pacemaker stop on other node

2013-11-11 Thread Vladislav Bogdanov
12.11.2013 03:15, Andrew Beekhof wrote: > Can you try with these two patches please? > > + Andrew Beekhof (4 seconds ago) fec946a: Fix: crmd: When the DC gracefully > shuts down, record the new expected state into the cib (HEAD, master) > + Andrew Beekhof (10 seconds ago) 740122a: Fix: crmd: Whe

Re: [Pacemaker] DRBD promotion timeout after pacemaker stop on other node

2013-11-11 Thread Vladislav Bogdanov
12.11.2013 03:05, Andrew Beekhof wrote: > > On 12 Nov 2013, at 10:29 am, Andrew Beekhof wrote: > >> >> On 12 Nov 2013, at 2:46 am, Vladislav Bogdanov wrote: >> >>> 11.11.2013 09:00, Vladislav Bogdanov wrote: >>> ... >>> Looking at crm-fence-peer.sh script, it would determine peer state as >

Re: [Pacemaker] DRBD promotion timeout after pacemaker stop on other node

2013-11-11 Thread Andrew Beekhof
Can you try with these two patches please? + Andrew Beekhof (4 seconds ago) fec946a: Fix: crmd: When the DC gracefully shuts down, record the new expected state into the cib (HEAD, master) + Andrew Beekhof (10 seconds ago) 740122a: Fix: crmd: When a peer expectedly shuts down, record the new jo

Re: [Pacemaker] DRBD promotion timeout after pacemaker stop on other node

2013-11-11 Thread Andrew Beekhof
On 12 Nov 2013, at 10:29 am, Andrew Beekhof wrote: > > On 12 Nov 2013, at 2:46 am, Vladislav Bogdanov wrote: > >> 11.11.2013 09:00, Vladislav Bogdanov wrote: >> ... >> Looking at crm-fence-peer.sh script, it would determine peer state as >> offline immediately if node state (all of) >

Re: [Pacemaker] DRBD promotion timeout after pacemaker stop on other node

2013-11-11 Thread Vladislav Bogdanov
11.11.2013 09:00, Vladislav Bogdanov wrote: ... Looking at crm-fence-peer.sh script, it would determine peer state as offline immediately if node state (all of) * doesn't contain "expected" tag or has it set to "down" * has "in_ccm" tag set to false * has "crmd" tag set to

Re: [Pacemaker] DRBD promotion timeout after pacemaker stop on other node

2013-11-10 Thread Vladislav Bogdanov
11.11.2013 06:32, Vladislav Bogdanov wrote: > 11.11.2013 02:30, Andrew Beekhof wrote: >> >> On 5 Nov 2013, at 2:22 am, Vladislav Bogdanov wrote: >> >>> Hi Andrew, David, all, >>> >>> Just found interesting fact, don't know is it a bug or not. >>> >>> When doing service pacemaker stop on a node whi

Re: [Pacemaker] DRBD promotion timeout after pacemaker stop on other node

2013-11-10 Thread Vladislav Bogdanov
11.11.2013 02:30, Andrew Beekhof wrote: > > On 5 Nov 2013, at 2:22 am, Vladislav Bogdanov wrote: > >> Hi Andrew, David, all, >> >> Just found interesting fact, don't know is it a bug or not. >> >> When doing service pacemaker stop on a node which has drbd resource >> promoted, that resource does

Re: [Pacemaker] DRBD promotion timeout after pacemaker stop on other node

2013-11-10 Thread Andrew Beekhof
On 5 Nov 2013, at 2:22 am, Vladislav Bogdanov wrote: > Hi Andrew, David, all, > > Just found interesting fact, don't know is it a bug or not. > > When doing service pacemaker stop on a node which has drbd resource > promoted, that resource does not promote on another node, and promote > operat

[Pacemaker] DRBD promotion timeout after pacemaker stop on other node

2013-11-04 Thread Vladislav Bogdanov
Hi Andrew, David, all, Just found interesting fact, don't know is it a bug or not. When doing service pacemaker stop on a node which has drbd resource promoted, that resource does not promote on another node, and promote operation timeouts. This is related to drbd fence integration with pacemake