Back to bug 1038709

Who When What Removed Added
Perry Myers 2013-12-05 16:35:25 UTC Assignee rhos-maint sdake
Perry Myers 2013-12-05 16:36:35 UTC Depends On 1038638
See Also https://bugzilla.redhat.com/show_bug.cgi?id=1038638
Steven Dake 2013-12-05 18:40:15 UTC Link ID OpenStack gerrit 60311
Steven Dake 2013-12-06 02:34:53 UTC Status NEW ASSIGNED
Jeff Peeler 2013-12-06 16:50:38 UTC CC jpeeler
Steven Dake 2013-12-06 17:57:20 UTC Link ID OpenStack gerrit 60486
Jeff Peeler 2013-12-06 19:39:37 UTC Status ASSIGNED MODIFIED
Fixed In Version openstack-heat-2013.2-4.el6ost
errata-xmlrpc 2013-12-09 21:22:19 UTC Status MODIFIED ON_QA
Bruce Reeler 2013-12-10 00:27:48 UTC CC breeler
Flags needinfo?(jpeeler)
Jeff Peeler 2013-12-10 05:15:47 UTC Doc Text Cause:
When the QPID broker restarts or fails over with fanout subscriptions.

Consequence:
Subscribed clients will attempt to re-establish their connections improperly, depending upon the version topology.

Fix:
Removes special-case reconnect code that manages UUID addresses; it is unnecessary.

Result:
Subscribed clients reconnect successfully.
Flags needinfo?(jpeeler)
Don Domingo 2013-12-11 06:43:25 UTC CC ddomingo
Doc Text Cause:
When the QPID broker restarts or fails over with fanout subscriptions.

Consequence:
Subscribed clients will attempt to re-establish their connections improperly, depending upon the version topology.

Fix:
Removes special-case reconnect code that manages UUID addresses; it is unnecessary.

Result:
Subscribed clients reconnect successfully.
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.

This caused qpidd to incorrectly establish multiple subscriptions on the same fanout address after reconnecting. The QPID broker only requires one subscription; each extra subscription created duplicate RPC notification samples for Heat.

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.
Don Domingo 2013-12-11 07:11:42 UTC 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.

This caused qpidd to incorrectly establish multiple subscriptions on the same fanout address after reconnecting. The QPID broker only requires one subscription; each extra subscription created duplicate RPC notification samples for Heat.

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.
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.

This caused qpidd to incorrectly establish multiple subscriptions on the same fanout address after reconnecting. The QPID broker only requires one subscription; each extra subscription created duplicate RPC notification samples for individual services (e.g. Heat).

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.
Ami Jeain 2013-12-16 08:55:45 UTC Keywords OtherQA
CC ajeain
Steven Dake 2013-12-16 14:31:24 UTC QA Contact kwhitney jpeeler
Jeff Peeler 2013-12-17 20:14:41 UTC Status ON_QA VERIFIED
errata-xmlrpc 2013-12-19 17:44:02 UTC Status VERIFIED RELEASE_PENDING
errata-xmlrpc 2013-12-20 00:33:01 UTC Status RELEASE_PENDING CLOSED
Resolution --- ERRATA
Last Closed 2013-12-19 19:33:01 UTC
Perry Myers 2016-04-26 21:35:48 UTC CC pmyers
Russell Bryant 2019-09-09 16:51:46 UTC CC rbryant

Back to bug 1038709