[Pacemaker] After pacemaker is stopped on DC, it gets fenced because last 'stop' operation is lost

Vladislav Bogdanov bubble at hoster-ok.com
Wed Aug 17 07:12:50 UTC 2011


17.08.2011 07:17, Andrew Beekhof wrote:
> On Tue, Aug 16, 2011 at 7:21 PM, Vladislav Bogdanov
> <bubble at hoster-ok.com> wrote:
>> Hi,
>>
>> I recently discovered that when I stop pacemaker on DC node (for
>> upgrade), that node is shortly fenced by a new DC.
>>
>> Fencing is caused by not-stopped (from the PoV of new DC) clone instance
>> (dlm in my case) which was actually stopped:
> 
> [snip]
> 
>> This is 100% reproducible in my setup, so I can take hb_report if this
>> is needed.
> 
> yes please

http://developerbugs.linux-foundation.org/show_bug.cgi?id=2634

> 
> _______________________________________________
> Pacemaker mailing list: Pacemaker at oss.clusterlabs.org
> http://oss.clusterlabs.org/mailman/listinfo/pacemaker
> 
> Project Home: http://www.clusterlabs.org
> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
> Bugs: http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker





More information about the Pacemaker mailing list