From: Aurelien DARRAGON <adarragon@haproxy.com>
Date: Fri, 21 Feb 2025 07:16:50 +0000 (+0100)
Subject: REGTESTS: fix reg-tests/server/abnsz.vtc
X-Git-Tag: v3.2-dev7~83
X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=26d97ec148d740214127477321cf1b0ebeef4e06;p=thirdparty%2Fhaproxy.git

REGTESTS: fix reg-tests/server/abnsz.vtc

It was proved in GH #2875 that the regtest was broken, at least for the
server-side abnsz, as the connect() was not performed using the proper
family, which results in kernel refusing to perform the call, while the
reg-test actually succeeds.

Indeed, in the test we used vtest client to connect to haproxy, which
then routed the request to another haproxy instance listening on an
abnsz socket, and this last haproxy was the one to answer the http
request.

As we only used "rxresp" in vtest client, the test succeeded with empty
responses, which was the case due to the server connection failing on the
first haproxy process.
---

diff --git a/reg-tests/server/abnsz.vtc b/reg-tests/server/abnsz.vtc
index f42933ed07..e1f3b1a715 100644
--- a/reg-tests/server/abnsz.vtc
+++ b/reg-tests/server/abnsz.vtc
@@ -28,6 +28,7 @@ haproxy h1 -Ws -S -conf {
 client c1 -connect ${h1_testme_sock} {
     txreq -url "/"
     rxresp
+    expect resp.status == 200
 } -run
 
 shell {