samba-mirror

mirror of https://github.com/samba-team/samba.git synced 2025-01-25 06:04:04 +03:00

25 lines

356 B

Bash

Raw Normal View History

ctdb-tests: Add a test for NAT gateway sanity checking Signed-off-by: Martin Schwenke <martin@meltin.net> 2014-03-17 06:15:39 +11:00			`#!/bin/sh`

			`. "${TEST_SCRIPTS_DIR}/unit.sh"`

			`define_test "missing config file"`

ctdb-tests: 11.natgw event script setup modularisation Signed-off-by: Martin Schwenke <martin@meltin.net> Reviewed-by: Amitay Isaacs <amitay@gmail.com> 2018-02-12 11:42:04 +11:00			`setup`

ctdb-tests: Add a test for NAT gateway sanity checking Signed-off-by: Martin Schwenke <martin@meltin.net> 2014-03-17 06:15:39 +11:00			`setup_ctdb_natgw <<EOF`
			`192.168.1.21 master`
			`192.168.1.22`
			`192.168.1.23`
			`192.168.1.24`
			`EOF`

			`rm -f "$CTDB_NATGW_NODES"`

			`required_result 1 <<EOF`
			`error: CTDB_NATGW_NODES=${CTDB_NATGW_NODES} unreadable`
			`EOF`

ctdb-eventscripts: Remove NAT gateway "monitor" event This event was introduced to handle misconfiguration. For example, where all nodes where configured as NAT gateway slaves. However, this event can fail when there are performance issues and capabilities can't be retrieved from a remote node. The problem is most likely with the remote node, so marking the local node UNHEALTHY is probably a mistake. Having a NAT gateway master node only matters in "ipreallocated", so leave it to do the checking. Given that a node will run "ipreallocated" as part of the first recovery, this should cause misconfigurations to be detected nice and early. Signed-off-by: Martin Schwenke <martin@meltin.net> Reviewed-by: Amitay Isaacs <amitay@gmail.com> 2014-07-25 16:56:57 +10:00			`for i in "startup" "ipreallocated" ; do`
ctdb-tests: Add a test for NAT gateway sanity checking Signed-off-by: Martin Schwenke <martin@meltin.net> 2014-03-17 06:15:39 +11:00			`simple_test_event "$i"`
			`done`

25 lines 356 B Bash Raw Normal View History Unescape Escape

25 lines

356 B

Bash

Raw Normal View History