hard coded http timeout in haproxy_server role template

Bug #1696703 reported by Chenjun Shen
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack-Ansible
Fix Released
Undecided
Chenjun Shen

Bug Description

Dear all,

In our private cloud, we experienced some timeout issues in haproxy.
Some API requests took more than 50 seconds.

As we found out in current haproxy_server role haproxy.cfg.j2 template. The timeout are unfortunately hard coded, and there is no variable which you could use to override them.

Snippet of current haproxy.cfg.j2 template.

-----------------------------------------------------------------
defaults
        log global
        option dontlognull
        option redispatch
        retries 3
        timeout client 50s
        timeout connect 10s
        timeout http-request {{ haproxy_http_request_timeout }}
        timeout server 50s
        maxconn 4096
-----------------------------------------------------------------

I will implement some new variables which could be used to override timeout.

Revision history for this message
Chenjun Shen (cshen) wrote :
tags: removed: haproxy timeout
Changed in openstack-ansible:
assignee: nobody → Chenjun Shen (cshen)
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to openstack-ansible-haproxy_server (master)

Reviewed: https://review.openstack.org/472200
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible-haproxy_server/commit/?id=88ec33a6c0b70c5f5cf72027d20d257de06a5cfd
Submitter: Jenkins
Branch: master

commit 88ec33a6c0b70c5f5cf72027d20d257de06a5cfd
Author: Chenjun Shen <email address hidden>
Date: Thu Jun 8 12:50:09 2017 +0200

    Replace hard coded timeout values with variables

    Currently the timeout values for client/connect/server are hard coded
    in templates/haproxy.cfg.j2. In order to give users flexibility to
    override these values, for example increase timeout or reduce timeout,
    I replaced hard coded timeout values with variables.

    The original default values are still kept in defaults/main.yml.

    Closes-Bug: #1696703

    Change-Id: I72e9691a074df04e9fb7c4ddc0fe610c8d13feff

Changed in openstack-ansible:
status: In Progress → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/openstack-ansible-haproxy_server 16.0.0.0b3

This issue was fixed in the openstack/openstack-ansible-haproxy_server 16.0.0.0b3 development milestone.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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