ctdb-daemon: Drop handling of ban control sent to unexpected node
authorMartin Schwenke <martin@meltin.net>
Wed, 29 Jul 2015 09:34:23 +0000 (19:34 +1000)
committerAmitay Isaacs <amitay@samba.org>
Fri, 4 Dec 2015 08:17:17 +0000 (09:17 +0100)
commitad6685847b18f63acb27d1bd998f0e757a6302eb
tree98bee40baa1abe619a65c6728e51f7ff52526259
parente153501474be47d8a6bdfa0dbf8fbb72ff74e319
ctdb-daemon: Drop handling of ban control sent to unexpected node

The banning code caters for the case where the node specified in the
bantime data is not the node receiving the control.  This never
happens.  There are 2 places where ctdb_ctrl_set_ban() is called: the
ctdb CLI tool and the recovery daemon.  Both pass the same node in the
bantime data that they are sending the control to.  There are no plans
to do anything more elaborate, so just delete the handling of this
special case.

Signed-off-by: Martin Schwenke <martin@meltin.net>
Reviewed-by: Amitay Isaacs <amitay@gmail.com>
ctdb/server/ctdb_banning.c