Bug 1082669
| Summary: | connection to multiple qpidd instances is broken | ||
|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Ihar Hrachyshka <ihrachys> |
| Component: | openstack-keystone | Assignee: | Nathan Kinder <nkinder> |
| Status: | CLOSED ERRATA | QA Contact: | Udi Kalifon <ukalifon> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 4.0 | CC: | aberezin, ajeain, ayoung, chrisw, ddomingo, fdinitto, fpercoco, gsim, kgiusti, lpeer, markmc, nkinder, yeylon |
| Target Milestone: | z5 | Keywords: | OtherQA, ZStream |
| Target Release: | 4.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | openstack-keystone-2013.2.3-9.el6ost | Doc Type: | Bug Fix |
| Doc Text: |
Previously, if the Identity service encountered a failed connection to a message broker, re-connection attempts kept failing as well. This was because the Identity service tried to reconnect to the same failing message broker, even if there were multiple hosts configured.
This has been fixed by making the reconnect() implementation select the next broker in the list. As a result, when multiple broker hosts are provided, it will try the next one in the list at every connection attempt.
This means that non-failure reconnect attempts will also switch from the current broker to the next in the list. Hence, users should not rely on any particular order when using brokers from the list.
|
Story Points: | --- |
| Clone Of: | 1082661 | Environment: | |
| Last Closed: | 2014-10-22 17:22:13 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: | 1036523, 1082670, 1082672 | ||
| Bug Blocks: | 1080561, 1082661, 1082664, 1082665, 1082666, 1082668, 1123376 | ||
|
Comment 3
Ami Jeain
2014-10-07 14:46:21 UTC
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/RHSA-2014-1688.html |