Bug 1057956
Summary: | It always exists some error message with "Failed to get information from haproxy" in the scale_events.log as it is normal | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Gaoyun Pei <gpei> |
Component: | ImageStreams | Assignee: | Brenton Leanhardt <bleanhar> |
Status: | CLOSED ERRATA | QA Contact: | libra bugs <libra-bugs> |
Severity: | low | Docs Contact: | |
Priority: | unspecified | ||
Version: | 2.2.0 | CC: | adellape, bleanhar, bmeng, jolamb, nwei |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | openshift-origin-cartridge-haproxy-1.17.3.4-1.el6op | Doc Type: | Bug Fix |
Doc Text: |
While successfully creating or scaling an application, the scale_events.log file on HAProxy cartridges displayed this error message: "Failed to get information from haproxy". This occurred due to common HAProxy operations and was potentially confusing because there was no actual problem. This bug fix suppresses the messages during such operations and now the logs do not show extraneous error messages. The following command must be run after applying this fix:
# oo-admin-upgrade upgrade-node --version=2.0.3
See the Solution section in the errata advisory for full details.
|
Story Points: | --- |
Clone Of: | 1044927 | Environment: | |
Last Closed: | 2014-02-25 15:44:03 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: | |||
Bug Depends On: | 1044927 | ||
Bug Blocks: |
Description
Gaoyun Pei
2014-01-26 07:06:55 UTC
verify this issue with openshift-origin-cartridge-haproxy-1.17.3.4-1.el6op Create a scalable app, scale-up and scale-down several times, check the scale_event.log, no "ERROR -- : Failed to get information from haproxy" appeared. 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-0209.html |