[Pacemaker] putting a DC into standby does not change the DC

[Andrew Beekhof]

On Feb 10, 2009, at 4:13 PM, Raoul Bhatia [IPAX] wrote:

> hi,
>
> i'm using pacemaker f228d820ba27.
>
> both nodes are online, wc01 is master:
>> ============
>> Last updated: Tue Feb 10 16:04:44 2009
>> Current DC: wc01 (31de4ab3-2d05-476e-8f9a-627ad6cd94ca)
>> Version: 1.0.1-node: f228d820ba27cc33ea5778224d8d2084119b588c
>> 2 Nodes configured.
>> 10 Resources configured.
>> ============
>
> i want to maintain (install, reboot, etc.) the node.
> the docs (configuration explained, page 49 (or 37 respectively) say:
>
>> There are primarily two occasions when you would want to move a
>> resource from it’s current location: when the whole node
>> is under maintenance and when a single resource needs to be moved.
>
> so i put wc01 into standby using "crm_standby -v on -N wc01".
> all resources are migrated but wc01 remains the current dc:
>
>
>> ============
>> Last updated: Tue Feb 10 16:10:03 2009
>> Current DC: wc01 (31de4ab3-2d05-476e-8f9a-627ad6cd94ca)
>> Version: 1.0.1-node: f228d820ba27cc33ea5778224d8d2084119b588c
>> 2 Nodes configured.
>> 10 Resources configured.
>> ============
>
> is this an intended behavior?

yes

> if so, can you please elaborate why?
> (not a priority of course).

let me ask a question back, why would it need to be somewhere else?