haproxy/reg-tests/server/cli_delete_server.vtc
Willy Tarreau f673923629 REGTESTS: extend the default I/O timeouts and make them overridable
With the CI occasionally slowing down, we're starting to see again some
spurious failures despite the long 1-second timeouts. This reports false
positives that are disturbing and doesn't provide as much value as this
could. However at this delay it already becomes a pain for developers
to wait for the tests to complete.

This commit adds support for the new environment variable
HAPROXY_TEST_TIMEOUT that will allow anyone to modify the connect,
client and server timeouts. It was set to 5 seconds by default, which
should be plenty for quite some time in the CI. All relevant values
that were 200ms or above were replaced by this one. A few larger
values were left as they are special. One test for the set-timeout
action that used to rely on a fixed 1-sec value was extended to a
fixed 5-sec, as the timeout is normally not reached, but it needs
to be known to compare the old and new values.
2021-11-18 17:57:11 +01:00

65 lines
2.0 KiB
Plaintext

# This script is to test the ability to remove servers, unless they are
# referenced by some elements from the configuration.
#
varnishtest "Delete server via cli"
feature cmd "$HAPROXY_PROGRAM -cc 'version_atleast(2.5-dev0)'"
feature ignore_unknown_macro
haproxy h1 -conf {
defaults
mode http
timeout connect "${HAPROXY_TEST_TIMEOUT-5s}"
timeout client "${HAPROXY_TEST_TIMEOUT-5s}"
timeout server "${HAPROXY_TEST_TIMEOUT-5s}"
frontend fe
bind "fd@${feS}"
acl s1_full srv_sess_rate(test/s1) gt 50
default_backend test
backend test
use-server s3 unless { always_false }
server s1 ${s1_addr}:${s1_port} # referenced in ACL
server s2 ${s1_addr}:${s1_port} check # referenced in track
server s3 ${s1_addr}:${s1_port} track s2 # referenced in use-server
server s4 ${s1_addr}:${s1_port} # removable server
} -start
haproxy h1 -cli {
# experimental mode disabled
send "del server test/s1"
expect ~ "This command is restricted to experimental mode only."
# non existent backend
send "experimental-mode on; del server foo/s1"
expect ~ "No such backend."
# non existent server
send "experimental-mode on; del server test/other"
expect ~ "No such server."
# server referenced in ACL
send "experimental-mode on; del server test/s1"
expect ~ "This server cannot be removed at runtime due to other configuration elements pointing to it."
# tracked server
send "experimental-mode on; del server test/s2"
expect ~ "This server cannot be removed at runtime due to other configuration elements pointing to it."
# tracked server
send "experimental-mode on; del server test/s3"
expect ~ "This server cannot be removed at runtime due to other configuration elements pointing to it."
# server in running mode
send "experimental-mode on; del server test/s4"
expect ~ "Only servers in maintenance mode can be deleted."
send "disable server test/s4"
expect ~ ".*"
# valid command
send "experimental-mode on; del server test/s4"
expect ~ "Server deleted."
}