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

[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 anything except "online"
>>>>
>>>> On the other hand, crmd sets "expected" = "down" only after fencing is
>>>> complete (probably the same for "in_ccm"?). Shouldn't is do the same (or
>>>> may be just remove that tag) if clean shutdown about to be complete?
>>>
>>> That would make sense.  Are you using the plugin, cman or corosync 2?
> 

This one works in all tests I was able to imagine, but I'm not sure it is
completely safe to set expected="down" for old DC (in test when drbd is promoted on DC and it reboots).