haproxy/reg-tests/connection/reverse_connect_full.vtc
Willy Tarreau 48d5ef363d REGTESTS: restrict execution to a single thread group
When threads are enabled and running on a machine with multiple CCX
or multiple nodes, thread groups are now enabled since 3.3-dev2, causing
load-balancing algorithms to randomly fail due to incoming connections
spreading over multiple groups and using different load balancing indexes.

Let's just force "thread-groups 1" into all configs when threads are
enabled to avoid this.
2025-06-30 18:54:35 +02:00

79 lines
1.4 KiB
Plaintext

varnishtest "Reverse connect full test"
feature ignore_unknown_macro
feature cmd "$HAPROXY_PROGRAM -cc 'version_atleast(2.9-dev0)'"
server s1 {
rxreq
txresp
} -start
haproxy h_edge -conf {
global
.if feature(THREAD)
thread-groups 1
.endif
expose-experimental-directives
defaults
log global
timeout connect "${HAPROXY_TEST_TIMEOUT-5s}"
timeout client "${HAPROXY_TEST_TIMEOUT-5s}"
timeout server "${HAPROXY_TEST_TIMEOUT-5s}"
mode http
frontend pub
bind "fd@${pub}"
use_backend be-reverse
frontend priv
bind "fd@${priv}" proto h2
tcp-request session attach-srv be-reverse/dev
backend be-reverse
server dev rhttp@
} -start
haproxy h_dev -conf {
global
.if feature(THREAD)
thread-groups 1
.endif
expose-experimental-directives
defaults
log global
timeout connect "${HAPROXY_TEST_TIMEOUT-5s}"
timeout client "${HAPROXY_TEST_TIMEOUT-5s}"
timeout server "${HAPROXY_TEST_TIMEOUT-5s}"
mode http
frontend fe
bind "rhttp@be-pre-connect/srv"
use_backend be
backend be-pre-connect
server srv ${h_edge_priv_addr}:${h_edge_priv_port} proto h2
backend be
server srv ${s1_addr}:${s1_port}
}
client c1 -connect ${h_edge_pub_sock} {
txreq -url "/"
rxresp
expect resp.status == 503
} -run
haproxy h_dev -start
# TODO replace delay by a proper wait
delay 3
client c1 -connect ${h_edge_pub_sock} {
txreq -url "/"
rxresp
expect resp.status == 200
} -run