Juju Charms Collection
openstack-dashboard package

haproxy timeout client 30000 and timeout server 30000 are hard coded even haproxy-client-timeout and haproxy-server-timeout are exposed via charm config

Bug #1566787 reported by Nobuto Murata
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
openstack-dashboard (Juju Charms Collection)
Fix Released
Undecided
Unassigned

Bug Description

Similar to Bug #1564214, templates/haproxy.cfg has hard coded values even charm config exposes haproxy-client-timeout and haproxy-server-timeout.

defaults
    log global
    mode tcp
    option tcplog
    option dontlognull
    retries 3
    timeout queue 1000
    timeout connect 1000
    timeout client 30000
    timeout server 30000

Revision history for this message
Nobuto Murata (nobuto) wrote :

Fixed by: https://github.com/openstack/charm-openstack-dashboard/commit/ebc4ca57caca7975477b85d8d11effe9fb520f70

Changed in openstack-dashboard (Juju Charms Collection):
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.