[Pacemaker] Node recover causes resource to migrate

[Andrew Beekhof]

On 24/07/2013, at 7:26 PM, Lars Marowsky-Bree <lmb at suse.com> wrote:

> On 2013-07-24T09:00:23, Andrew Beekhof <andrew at beekhof.net> wrote:
> 
>>> 4. Node A is back with a different internal ip address.
>> 
>> This is your basic problem.
>> 
>> I don't believe there is any cluster software that is designed to support this sort of scenario.
>> Even at the corosync level, it has no knowledge that this is the same machine that left. 
> 
> Statically assigned nodeids?

Wouldn't hurt, but you still need to bring down the still-active node to get it to talk to the new node.
Which sucks