Back to bug 1038710

Who When What Removed Added
Perry Myers 2013-12-05 16:35:33 UTC Assignee rhos-maint eglynn
Perry Myers 2013-12-05 16:36:35 UTC Depends On 1038638
See Also https://bugzilla.redhat.com/show_bug.cgi?id=1038638
Eoghan Glynn 2013-12-05 22:28:07 UTC Status NEW ASSIGNED
Eoghan Glynn 2013-12-05 22:29:18 UTC Link ID OpenStack gerrit 60371
Eoghan Glynn 2013-12-06 12:38:25 UTC Link ID OpenStack gerrit 60483
Eoghan Glynn 2013-12-06 15:08:24 UTC Status ASSIGNED POST
Pádraig Brady 2013-12-06 15:45:44 UTC Status POST MODIFIED
Fixed In Version openstack-ceilometer-2013.2-4.el6ost
Eoghan Glynn 2013-12-06 16:00:46 UTC Keywords OtherQA
Dafna Ron 2013-12-06 16:05:18 UTC CC dron
errata-xmlrpc 2013-12-06 19:36:54 UTC Status MODIFIED ON_QA
Bruce Reeler 2013-12-09 07:04:10 UTC CC breeler, eglynn
Flags needinfo?(eglynn)
Eoghan Glynn 2013-12-09 17:49:26 UTC Doc Text Cause: a defect in the QPID topic consumer re-connection logic under the v2 topology caused a malformed subscriber address to be used after a qpidd restart.

Consequence: samples derived from RPC notifications after a qpidd restart were duplicated due to the multiple subscriptions being established on same fanout address after reconnection .

Fix: remove the special-case reconnect logic that manages UUID addresses, which is unnecessary as the QPID broker will generate unique queue names automatically when clients reconnect.

Result: the prior duplication of samples derived from notifications no longer occurs.
Flags needinfo?(eglynn)
Don Domingo 2013-12-11 06:39:24 UTC CC ddomingo
Doc Text Cause: a defect in the QPID topic consumer re-connection logic under the v2 topology caused a malformed subscriber address to be used after a qpidd restart.

Consequence: samples derived from RPC notifications after a qpidd restart were duplicated due to the multiple subscriptions being established on same fanout address after reconnection .

Fix: remove the special-case reconnect logic that manages UUID addresses, which is unnecessary as the QPID broker will generate unique queue names automatically when clients reconnect.

Result: the prior duplication of samples derived from notifications no longer occurs.
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 Ceilometer.

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:45 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 Ceilometer.

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

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.
Eoghan Glynn 2013-12-11 16:59:15 UTC Status ON_QA VERIFIED
errata-xmlrpc 2013-12-19 17:44:07 UTC Status VERIFIED RELEASE_PENDING
errata-xmlrpc 2013-12-20 00:41:18 UTC Status RELEASE_PENDING CLOSED
Resolution --- ERRATA
Last Closed 2013-12-19 19:41:18 UTC
John Skeoch 2014-02-02 22:41:05 UTC CC srevivo
Perry Myers 2016-04-26 23:11:03 UTC CC pmyers
Russell Bryant 2019-09-09 14:22:10 UTC CC rbryant

Back to bug 1038710