haproxy often breaks mysql connections

Bug #1645098 reported by Vladislav Belogrudov
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
kolla
Expired
Undecided
Unassigned
kolla-ansible
Fix Released
Undecided
Unassigned

Bug Description

haproxy has very small timeout values for mysql connections that often results in "server lost connection" messages and is quite dangerous during heavy upgrades. Looking into elsewhere (RHOS, openstack-ansible, etc) I suggest to increase it to 3600s which is default for idle timeouts in OpenStack projects.

Changed in kolla:
assignee: nobody → Vladislav Belogrudov (vlad-belogrudov)
Changed in kolla:
status: New → Triaged
importance: Undecided → High
Changed in kolla:
milestone: none → ocata-3
milestone: ocata-3 → ocata-2
Changed in kolla-ansible:
milestone: none → ocata-2
Changed in kolla:
milestone: ocata-2 → 3.0.2
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to kolla-ansible (master)

Reviewed: https://review.openstack.org/403428
Committed: https://git.openstack.org/cgit/openstack/kolla-ansible/commit/?id=d2c4f3d14ae01f782545b1c139e433de2d4bf472
Submitter: Jenkins
Branch: master

commit d2c4f3d14ae01f782545b1c139e433de2d4bf472
Author: Vladislav Belogrudov <email address hidden>
Date: Sun Nov 27 13:50:39 2016 +0300

    Icrease haproxy timeouts for mysql connections

    Haproxy often breaks mysql connections that results in
    "MySQL server has gone away" or similar because of 1 minute
    timeouts. Instead the timeouts should be not less than mysql
    connections timeouts - in most cases set to 3600s by default
    by OpenStack projects.

    Change-Id: Ic364f6942cdc6c2f274a508ae548bf964b098da4
    Closes-Bug: #1645098

Changed in kolla-ansible:
status: New → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/kolla-ansible 4.0.0.0b2

This issue was fixed in the openstack/kolla-ansible 4.0.0.0b2 development milestone.

Changed in kolla:
milestone: 3.0.2 → 3.0.3
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to kolla (stable/newton)

Fix proposed to branch: stable/newton
Review: https://review.openstack.org/435760

Revision history for this message
OpenStack Infra (hudson-openstack) wrote :

Fix proposed to branch: stable/newton
Review: https://review.openstack.org/436121

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on kolla (stable/newton)

Change abandoned by Magnus Lööf (<email address hidden>) on branch: stable/newton
Review: https://review.openstack.org/435760
Reason: https://review.openstack.org/#/c/436121/

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to kolla (stable/newton)

Reviewed: https://review.openstack.org/436121
Committed: https://git.openstack.org/cgit/openstack/kolla/commit/?id=0c8bbfb23077f9d6f127fff26b5e34b7f9fba3e1
Submitter: Jenkins
Branch: stable/newton

commit 0c8bbfb23077f9d6f127fff26b5e34b7f9fba3e1
Author: Vladislav Belogrudov <email address hidden>
Date: Sun Nov 27 13:50:39 2016 +0300

    Icrease haproxy timeouts for mysql connections

    Haproxy often breaks mysql connections that results in
    "MySQL server has gone away" or similar because of 1 minute
    timeouts. Instead the timeouts should be not less than mysql
    connections timeouts - in most cases set to 3600s by default
    by OpenStack projects.

    Change-Id: Ic364f6942cdc6c2f274a508ae548bf964b098da4
    Closes-Bug: #1645098
    (cherry picked from commit d2c4f3d14ae01f782545b1c139e433de2d4bf472)

tags: added: in-stable-newton
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/kolla 3.0.3

This issue was fixed in the openstack/kolla 3.0.3 release.

Changed in kolla:
milestone: 3.0.3 → 3.0.4
Revision history for this message
Jeffrey Zhang (jeffrey4l) wrote : Cleanup EOL bug report

This is an automated cleanup. This bug report has been closed because it
is older than 18 months and there is no open code change to fix this.
After this time it is unlikely that the circumstances which lead to
the observed issue can be reproduced.

If you can reproduce the bug, please:
* reopen the bug report (set to status "New")
* AND add the detailed steps to reproduce the issue (if applicable)
* AND leave a comment "CONFIRMED FOR: <RELEASE_NAME>"
  Only still supported release names are valid (OCATA, PIKE, QUEENS, ROCKY, ROCKY).
  Valid example: CONFIRMED FOR: OCATA

Changed in kolla:
assignee: Vladislav Belogrudov (vlad-belogrudov) → nobody
importance: High → Undecided
status: Triaged → Expired
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.