Comment 37 for bug 2045168

Reviewed: https://review.opendev.org/c/openstack/charm-openstack-dashboard/+/915008
Committed: https://opendev.org/openstack/charm-openstack-dashboard/commit/fb63730e63fb09919d8b24c4ce34c77c85bb1317
Submitter: "Zuul (22348)"
Branch: stable/xena

commit fb63730e63fb09919d8b24c4ce34c77c85bb1317
Author: Rodrigo Barbieri <email address hidden>
Date: Wed Mar 6 14:59:11 2024 -0300

    Adjust haproxy timeout to intended values

    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 09c587116059319305b2a09cb393a084a52d1fc9)
    (cherry picked from commit 2f430d15e64766fce4dc398ee23703a395693027)
    (cherry picked from commit f013b18c7680174dcbc4217030081a451347c8ef)
    (cherry picked from commit f6f60a37ba99fd56fd02ac1a4c518703e9d9efca)
    (cherry picked from commit 62777b150b1753a5a33e16c6dbfce24bc828a9dd)