tree d8f15f6e90adcad861df1b90585a739d6cea69ae
parent 623401b983185c1e0f6507e96557de3bc46fd41b
author Simon Horman <horms@verge.net.au> 1424917577 +0900
committer Willy Tarreau <w@1wt.eu> 1424930930 +0100
encoding latin1

BUG/MEDIUM: Do not consider an agent check as failed on L7 error

As failure to connect to the agent check is not sufficient to mark it as
failed it stands to reason that an L7 error shouldn't either.

Without this fix if an L7 error occurs, for example of connectivity to the
agent is lost immediately after establishing a connection to it, then the
agent check will be considered to have failed and thus may end up with zero
health. Once this has occurred if the primary health check also reaches
zero health, which is likely if connectivity to the server is lost, then
the server will be marked as down and not be marked as up again until a
successful agent check occurs regardless of the success of any primary
health checks.

This behaviour is not correct as a failed agent check should never cause a
server to be marked as down or by extension continue to be marked as down.

Signed-off-by: Simon Horman <horms@verge.net.au>
(cherry picked from commit eaabd52e29a29187f9829fe727028a6ca530cbf9)