| Summary: | [oslo] With QPID, RPC calls to a topic are always fanned-out to all subscribers. | |||
|---|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Ken Giusti <kgiusti> | |
| Component: | openstack-nova | Assignee: | Vladan Popovic <vpopovic> | |
| Status: | CLOSED ERRATA | QA Contact: | Jakub Ruzicka <jruzicka> | |
| Severity: | high | Docs Contact: | ||
| Priority: | high | |||
| Version: | unspecified | CC: | apevec, breeler, dallan, ddomingo, fpercoco, hateya, jhenner, ndipanov, sclewis, vpopovic, yeylon | |
| Target Milestone: | rc | Keywords: | OtherQA, TestOnly | |
| Target Release: | 4.0 | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| Fixed In Version: | openstack-nova-2013.2-9.el6ost | Doc Type: | Bug Fix | |
| Doc Text: |
When the QPID broker is restarted, RPC servers attempt to re-connect. However, a bug in the QPID topic consumer re-connection logic (under the v2 topology) caused qpidd to use a malformed subscriber address after restarting.
As a result, RPC requests sent to a topic with multiple servers ended up being incorrectly multicast to all servers.
This release removes the special-case reconnect logic that handles UUID addresses, which in turn avoids the incorrect establishment of multiple subscription to the same fanout address. The QPID broker will simply generate unique queue names automatically when clients reconnect.
|
Story Points: | --- | |
| Clone Of: | ||||
| : | 1038714 1038716 1038717 1038718 1045066 (view as bug list) | Environment: | ||
| Last Closed: | 2013-12-20 00:32:53 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: | ||
| Bug Depends On: | ||||
| Bug Blocks: | 1045066 | |||
|
Description
Ken Giusti
2013-12-05 14:39:42 UTC
This seems important enough to be an RC blocker for 4.0. But doesn't this bug need to be cloned to Nova, Ceilometer, Neutron, etc (every component that copies and pastes the code from Oslo for RPC?) (In reply to Perry Myers from comment #3) > This seems important enough to be an RC blocker for 4.0. But doesn't this > bug need to be cloned to Nova, Ceilometer, Neutron, etc (every component > that copies and pastes the code from Oslo for RPC?) It's an important fix, for sure. Note that it doesn't affect the default configuration. This only affects if the v2 topology is enabled. So, it doesn't necessarily have to be a blocker, but we'd need a release note saying not to use the v2 topology at all yet. We should get this in if we can and avoid that. 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/RHEA-2013-1859.html *** Bug 1045066 has been marked as a duplicate of this bug. *** |