From 59b313832af476377aaba40ecc7ee4e166c922d8 Mon Sep 17 00:00:00 2001
From: William Lallemand <wlallemand@haproxy.com>
Date: Mon, 13 Nov 2023 14:38:36 +0100
Subject: [PATCH] REGTESTS: startup: -conf-OK requires -V with current VTest

Current version of VTest tests the output of "haproxy -c" instead of the
return code. Since we don't output anymore when the configuration is
valid, this broke the test. (a06f621).

This fixes the issue by adding the -V when doing a -conf-OK. But this
must fixed in VTest.
---
 reg-tests/startup/default_rules.vtc | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/reg-tests/startup/default_rules.vtc b/reg-tests/startup/default_rules.vtc
index cd86f7414..1cbbfa935 100644
--- a/reg-tests/startup/default_rules.vtc
+++ b/reg-tests/startup/default_rules.vtc
@@ -127,7 +127,7 @@ haproxy h13 -conf-BAD {} {
         bind "fd@${feh10}"
 }
 
-haproxy h14 -conf-OK {
+haproxy h14 -arg -V -conf-OK {
     defaults tcp
         tcp-response inspect-delay 5s
         tcp-response content accept
@@ -162,7 +162,7 @@ haproxy h16 -conf-BAD {} {
         server www 127.0.0.1:80
 }
 
-haproxy h17 -conf-OK {
+haproxy h17 -arg -V -conf-OK {
     defaults common
         mode http