haproxy/reg-tests/stream/unique-id.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

53 lines
1.1 KiB
Plaintext

varnishtest "unique-id test"
feature ignore_unknown_macro
server s1 {
rxreq
txresp
} -repeat 2 -start
haproxy h1 -conf {
global
.if feature(THREAD)
thread-groups 1
.endif
defaults
mode http
timeout connect "${HAPROXY_TEST_TIMEOUT-5s}"
timeout client "${HAPROXY_TEST_TIMEOUT-5s}"
timeout server "${HAPROXY_TEST_TIMEOUT-5s}"
frontend stable
bind "fd@${fe1}"
unique-id-format TEST-%[uuid]
http-response set-header A %[unique-id]
http-response set-header B %[unique-id]
default_backend be
frontend request_data
bind "fd@${fe2}"
unique-id-format TEST-%[req.hdr(in)]
http-response set-header out %[unique-id]
default_backend be
backend be
server srv1 ${s1_addr}:${s1_port}
} -start
client c1 -connect ${h1_fe1_sock} {
txreq -url "/"
rxresp
expect resp.status == 200
expect resp.http.a == resp.http.b
} -run
client c2 -connect ${h1_fe2_sock} {
txreq -url "/" \
-hdr "in: 12345678"
rxresp
expect resp.status == 200
expect resp.http.out == "TEST-12345678"
} -run