Bug 1160562
Summary: | openshift-sni-proxy restart command needs call 'oo-rebuild-haproxy-sni-proxy' function | |||
---|---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | xjia <xjia> | |
Component: | Containers | Assignee: | Brenton Leanhardt <bleanhar> | |
Status: | CLOSED ERRATA | QA Contact: | libra bugs <libra-bugs> | |
Severity: | medium | Docs Contact: | ||
Priority: | medium | |||
Version: | 2.2.0 | CC: | adellape, anli, bleanhar, bperkins, jokerman, libra-onpremise-devel, lmeyer, mmccomas, xtian | |
Target Milestone: | --- | Keywords: | Upstream | |
Target Release: | --- | |||
Hardware: | Unspecified | |||
OS: | Unspecified | |||
Whiteboard: | ||||
Fixed In Version: | rubygem-openshift-origin-frontend-haproxy-sni-proxy-0.4.2-1 | Doc Type: | Bug Fix | |
Doc Text: |
Restarting the openshift-sni-proxy service did not call the oo-rebuild-haproxy-sni-proxy function, which is required to rebuild the HAProxy configuration. As a result, if SNI proxy plug-in configuration changes had been made, they were not reflected on a service restart. This bug fix updates the SNI proxy plug-in and now a rebuild of the configuration is initiated prior to startup when either starting or restarting the openshift-sni-proxy service.
|
Story Points: | --- | |
Clone Of: | ||||
: | 1161135 1161136 (view as bug list) | Environment: | ||
Last Closed: | 2014-12-10 13:25:00 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: | 1161135 | |||
Bug Blocks: |
Description
xjia
2014-11-05 07:36:31 UTC
Can this bug be fixed in OSE-2.1.9? It's very easy to fix. Xuan Jia <xjia> updated the status of jira ENTESB-2162 to Closed Checked in puddle-2-2-2014-11-24 oo-rebuild-haproxy-sni-proxy was moved to start. /etc/init.d/openshift-sni-proxy {start|stop|status|restart|try-restart|reload|try-reload|force-reload} works 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. https://rhn.redhat.com/errata/RHBA-2014-1979.html |