Many years ago change Ida7949113594b9b859ab7b4ba8b2bb440bab6e7d
attempted to change the timeouts of haproxy but did not succeed,
as deployments were still using the values from the charm's
templates/haproxy.cfg file, being effectively set to 30 seconds
and causing timeouts (see bug). Additionally, the description
of the config options became inaccurate, stating the default to
be a value that they were really not.
This patch addresses the timeout value discrepancy, adjusting
to the original change's intended values.
Closes-bug: #2045168
Change-Id: I83405727b4a116ec6f47b61211bf8ef3d2d9fbd6
(cherry picked from commit 09c5871160)
(cherry picked from commit 2f430d15e6)
(cherry picked from commit f013b18c76)
(cherry picked from commit f6f60a37ba)
(cherry picked from commit 62777b150b)
fb63730e63