Bug 1167707
| Summary: | openshift-routing-daemon miss stomp connection after activemq is restarted and does not reconnect. | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Johnny Liu <jialiu> |
| Component: | Node | Assignee: | chris alfonso <calfonso> |
| Status: | CLOSED ERRATA | QA Contact: | libra bugs <libra-bugs> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 2.2.0 | CC: | adellape, bleanhar, hbrock, jokerman, libra-onpremise-devel, mmccomas |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | rubygem-openshift-origin-routing-daemon-0.20.2.3-1.el6op | Doc Type: | Bug Fix |
| Doc Text: |
In OpenShift Enterprise environments using the routing daemon, if the ActiveMQ service is restarted, the routing daemon did not reconnect to ActiveMQ automatically, and the openshift-routing-daemon service had to be restarted as well. This bug fix updates the routing daemon to now attempt to reconnect automatically after losing its ActiveMQ connection, and as a result this scenario no longer requires manual intervention.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2014-12-10 13:25:27 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
Johnny Liu
2014-11-25 09:58:43 UTC
PR is open for enterprise-server. https://github.com/openshift/enterprise-server/pull/450 Verified this bug with rubygem-openshift-origin-routing-daemon-0.20.2.3-1.el6op.noarch, and PASS. During activemq host is restarting, the following log is seen: ==> /var/log/openshift-routing-daemon.output <== connect to 10.66.79.143 failed: Connection refused - connect(2) will retry(#0) in 0.01 connect to 10.66.79.157 failed: Connection refused - connect(2) will retry(#1) in 0.02 connect to 10.66.79.143 failed: Connection refused - connect(2) will retry(#2) in 0.04 connect to 10.66.79.157 failed: Connection refused - connect(2) will retry(#3) in 0.08 connect to 10.66.79.143 failed: Connection refused - connect(2) will retry(#4) in 0.16 connect to 10.66.79.157 failed: Connection refused - connect(2) will retry(#5) in 0.32 connect to 10.66.79.143 failed: Connection refused - connect(2) will retry(#6) in 0.64 connect to 10.66.79.157 failed: Connection refused - connect(2) will retry(#7) in 1.28 connect to 10.66.79.143 failed: Connection refused - connect(2) will retry(#8) in 2.56 connect to 10.66.79.157 failed: Connection refused - connect(2) will retry(#9) in 5.12 connect to 10.66.79.143 failed: Connection refused - connect(2) will retry(#10) in 10.24 connect to 10.66.79.157 failed: Connection refused - connect(2) will retry(#11) in 20.48 connect to 10.66.79.143 failed: Connection refused - connect(2) will retry(#12) in 30.0 ==> /var/log/openshift/routing-daemon.log <== I, [2014-11-26T11:33:10.184076 #16964] INFO -- : Subscribing to /topic/routinginfo... After activemq service came back, scalable app is created successfully, and nginx conf files are built successfully. 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 |