Bug 1123300
Summary: | Rubygem-staypuft: HA: all "check" options are missing the interval parameter. This can cause higher recovery times in case of failure. | ||
---|---|---|---|
Product: | Red Hat OpenStack | Reporter: | Leonid Natapov <lnatapov> |
Component: | openstack-foreman-installer | Assignee: | Crag Wolfe <cwolfe> |
Status: | CLOSED ERRATA | QA Contact: | Leonid Natapov <lnatapov> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 5.0 (RHEL 7) | CC: | aberezin, cwolfe, dnavale, jguiditt, mburns, morazi, rhos-maint, yeylon |
Target Milestone: | ga | ||
Target Release: | Installer | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | openstack-foreman-installer-2.0.19-1.el6ost | Doc Type: | Bug Fix |
Doc Text: |
Previously, configuration parameter 'check' was missing the 'interval' option defined in HA Proxy which resulted in longer recovery times in case of failure.
With this update, a new configuration option 'check inter 1s' is added to /etc/haproxy/haproxy.cfg file and as a result, service recover as expected after failures.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2014-08-21 18:06:18 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Leonid Natapov
2014-07-25 09:18:52 UTC
Pull request: https://github.com/redhat-openstack/astapor/pull/337 Merged openstack-foreman-installer-2.0.20-1.el6ost "check inter 1s" appears as expected throughout /etc/haproxy/haproxy.cfg example: listen neutron-api bind 192.168.0.98:9696 mode tcp option tcplog server mac047d7b627d5a.example.com 192.168.0.2:9696 check inter 1s server mac047d7b685a04.example.com 192.168.0.5:9696 check inter 1s server mac047d7b61754e.example.com 192.168.0.3:9696 check inter 1s Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2014-1090.html |