haproxy/reg-tests/server/cli_add_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

92 lines
2.1 KiB
Plaintext

varnishtest "Add server via cli"
feature ignore_unknown_macro
#REQUIRE_VERSION=2.4
server s1 {
rxreq
txresp
} -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
balance random
backend other
balance static-rr
backend other2
balance random
mode tcp
} -start
client c1 -connect ${h1_feS_sock} {
txreq
rxresp
expect resp.status == 503
} -run
haproxy h1 -cli {
# experimental mode disabled
send "add server foo/s1 ${s1_addr}:${s1_port}"
expect ~ "This command is restricted to experimental mode only."
# non existent backend
send "experimental-mode on; add server foo/s1 ${s1_addr}:${s1_port}"
expect ~ "No such backend."
# missing address
send "experimental-mode on; add server test/s1"
expect ~ "'server' expects <name> and <addr>\\[:<port>\\] as arguments."
# invalid load-balancing algo
send "experimental-mode on; add server other/s1 ${s1_addr}:${s1_port}"
expect ~ "Backend must use a dynamic load balancing to support dynamic servers."
# invalid mux proto
send "experimental-mode on; add server other2/s1 ${s1_addr}:${s1_port} proto h2"
expect ~ "MUX protocol is not usable for server."
# valid command
send "experimental-mode on; add server test/s1 ${s1_addr}:${s1_port}"
expect ~ "New server registered."
# duplicate server
send "experimental-mode on; add server test/s1 ${s1_addr}:${s1_port}"
expect ~ "Already exists a server with the same name in backend."
# valid command
# specify the proto, it should be accepted for this backend
send "experimental-mode on; add server test/s2 ${s1_addr}:${s1_port} proto h2"
expect ~ "New server registered."
}
# dynamic servers are created on MAINT mode and should not be available at first
client c2 -connect ${h1_feS_sock} {
txreq
rxresp
expect resp.status == 503
} -run
haproxy h1 -cli {
send "enable server test/s1"
expect ~ ".*"
}
client c3 -connect ${h1_feS_sock} {
txreq
rxresp
expect resp.status == 200
} -run