REGTESTS: healthcheckmail: Relax matching on the healthcheck log message
Depending on the timing, the conneciton on lisrv listener may be fully accepted before any reject. Thus, instead of getting a socket error, an invalid L7 response is reported. There is no reason to be strick on the error type. Any failure is good here, because we just want to test the email-alert feature. This patch should fix issue #1857. It may be backported as far as 2.2. (cherry picked from commit 28bc152aa4a42ba91818aaf2af33ccb76f75a426) Signed-off-by: Christopher Faulet <cfaulet@haproxy.com>
This commit is contained in:
parent
a5f7291252
commit
852411765e
@ -5,7 +5,7 @@ feature ignore_unknown_macro
|
|||||||
|
|
||||||
syslog S1 -level notice {
|
syslog S1 -level notice {
|
||||||
recv
|
recv
|
||||||
expect ~ "[^:\\[ ]\\[${h1_pid}\\]: Health check for server be1/srv1 failed.+reason: Socket error.+info: \".+\".+check duration: [[:digit:]]+ms.+status: 0/1 DOWN."
|
expect ~ "[^:\\[ ]\\[${h1_pid}\\]: Health check for server be1/srv1 failed.+check duration: [[:digit:]]+ms.+status: 0/1 DOWN."
|
||||||
recv info
|
recv info
|
||||||
expect ~ "[^:\\[ ]\\[${h1_pid}\\]: Result=SUCCESS Bytes=[[:digit:]]+"
|
expect ~ "[^:\\[ ]\\[${h1_pid}\\]: Result=SUCCESS Bytes=[[:digit:]]+"
|
||||||
} -start
|
} -start
|
||||||
|
Loading…
x
Reference in New Issue
Block a user