tree 953edfc05402f04f47ef187de383f93477771643
parent 7eda849dce7b93cda5ccf703edaed59b5e28b8bd
author Simon Horman <horms@verge.net.au> 1415775353 +0900
committer Willy Tarreau <w@1wt.eu> 1422028061 +0100
encoding latin1

BUG/MEDIUM: Do not set agent health to zero if server is disabled in config

disable starts a server in the disabled state, however setting the health
of an agent implies that the agent is disabled as well as the server.

This is a problem because the state of the agent is not restored if
the state of the server is subsequently updated leading to an
unexpected state.

For example, if a server is started disabled and then the server
state is set to ready then without this change show stat indicates
that the server is "DOWN (agent)" when it is expected that the server
would be UP if its (non-agent) health check passes.

Reported-by: Mark Brooks <mark@loadbalancer.org>
Signed-off-by: Simon Horman <horms@verge.net.au>