1
0
mirror of http://git.haproxy.org/git/haproxy.git/ synced 2024-12-24 05:32:21 +00:00
haproxy/reg-tests/server/cli_delete_dynamic_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

99 lines
2.0 KiB
Plaintext

# This script is to test the proper behavior with dynamic servers insertion and
# deletion, in particular with the load-balancing of requests.
#
varnishtest "Delete server via cli"
feature ignore_unknown_macro
#REQUIRE_VERSION=2.4
# static server
server s1 -repeat 3 {
rxreq
txresp \
-body "resp from s1"
} -start
# use as a dynamic server, added then deleted via CLI
server s2 -repeat 3 {
rxreq
txresp \
-body "resp from s2"
} -start
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}"
default_backend test
backend test
server s1 ${s1_addr}:${s1_port}
} -start
# add a new dynamic server to be able to delete it then
haproxy h1 -cli {
# add a dynamic server and enable it
send "experimental-mode on; add server test/s2 ${s2_addr}:${s2_port}"
expect ~ "New server registered."
send "enable server test/s2"
expect ~ ".*"
}
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."
}
# first check that both servers are active
client c1 -connect ${h1_feS_sock} {
txreq
rxresp
expect resp.body == "resp from s1"
txreq
rxresp
expect resp.body == "resp from s2"
} -run
# delete the dynamic server
haproxy h1 -cli {
# server not in maintenance mode
send "experimental-mode on; del server test/s2"
expect ~ "Only servers in maintenance mode can be deleted."
send "disable server test/s2"
expect ~ ".*"
# valid command
send "experimental-mode on; del server test/s2"
expect ~ "Server deleted."
}
# now check that only the first server is used
client c2 -connect ${h1_feS_sock} {
txreq
rxresp
expect resp.body == "resp from s1"
txreq
rxresp
expect resp.body == "resp from s1"
} -run