[ClusterLabs] set node in maintenance - stop corosync - node is fenced - is that correct ?

[Lars Ellenberg]

On Mon, Oct 16, 2017 at 09:20:52PM +0200, Lentes, Bernd wrote:
> ----- On Oct 16, 2017, at 7:38 PM, Digimer lists at alteeve.ca wrote:
> > On 2017-10-16 01:24 PM, Lentes, Bernd wrote:
> >> i have the following behavior: I put a node in maintenance mode, afterwards stop
> >> corosync on that node with /etc/init.d/openais stop.
> >> This node is immediately fenced. Is that expected behavior ? I thought putting a
> >> node into maintenance does mean the cluster does not care anymore about that
> >> node.

> OS is SLES 11 SP4. That's not the most recent one.
> Pacmekaer is 1.1.12.
> I didn't plan to remove the node, but to do some maintenance on it.
> 
> If i put the node in standby, then i can invoke "/etc/init.d/openais
> stop" without that node getting fenced.
> But then all resources on that node are stopped/migrated. If i don't
> want that, i thought maintenance is the right way.
> Am i wrong ?
> 
> Ah, i just saw that i wasn't complete clear. The node is fenced after
> stopping openais, not after putting it into maintenance.
> I did that via "crm node maintenance <node>"

from the Changelog:

Changes since Pacemaker-1.1.15
  ...
  + pengine: do not fence a node in maintenance mode if it shuts down cleanly
  ...

just saying ... may or may not be what you are seeing.

Short term "workaround" may be to do things differently.
Maybe just set the cluster wide maintenance mode, not per node?

What are you really trying to do,
what is the reason you need it in maintenance-mode
and stop pacemaker/corosync/openais/the clusterstack,
but do not want to stop/migrate off the resources,
as would be done with "standby"?

-- 
: Lars Ellenberg
: LINBIT | Keeping the Digital World Running
: DRBD -- Heartbeat -- Corosync -- Pacemaker
: R&D, Integration, Ops, Consulting, Support

DRBD® and LINBIT® are registered trademarks of LINBIT