Back to bug 1038638

Who When What Removed Added
RHEL Program Management 2013-12-05 14:49:19 UTC Target Release --- 4.0
Dave Allan 2013-12-05 15:12:09 UTC Status NEW ASSIGNED
CC dallan
Assignee rhos-maint ndipanov
Perry Myers 2013-12-05 16:29:29 UTC CC pmyers
Flags needinfo?(rbryant)
Perry Myers 2013-12-05 16:30:51 UTC Priority unspecified high
Target Milestone --- rc
Severity unspecified high
Perry Myers 2013-12-05 16:34:23 UTC Blocks 1038709
Perry Myers 2013-12-05 16:34:31 UTC Blocks 1038710
Perry Myers 2013-12-05 16:34:40 UTC Blocks 1038711
Perry Myers 2013-12-05 16:34:46 UTC Blocks 1038712
Perry Myers 2013-12-05 16:36:35 UTC See Also https://bugzilla.redhat.com/show_bug.cgi?id=1038709, https://bugzilla.redhat.com/show_bug.cgi?id=1038710, https://bugzilla.redhat.com/show_bug.cgi?id=1038711, https://bugzilla.redhat.com/show_bug.cgi?id=1038712
Blocks 1038709, 1038710, 1038711, 1038712
Russell Bryant 2013-12-05 17:01:06 UTC Flags needinfo?(rbryant)
Steven Dake 2013-12-05 22:25:15 UTC CC sdake
Flags needinfo?(rbryant)
Russell Bryant 2013-12-06 01:10:11 UTC Flags needinfo?(rbryant)
Flavio Percoco 2013-12-06 10:34:11 UTC Status ASSIGNED ON_DEV
CC fpercoco
Link ID OpenStack gerrit 60468
Xavier Queralt 2013-12-06 13:51:04 UTC CC xqueralt
Assignee ndipanov vpopovic
Vladan Popovic 2013-12-06 13:57:30 UTC Status ON_DEV POST
Vladan Popovic 2013-12-06 16:04:35 UTC Status POST MODIFIED
Fixed In Version openstack-nova-2013.2-9.el6ost
Vladan Popovic 2013-12-09 15:55:11 UTC Keywords OtherQA
Jaroslav Henner 2013-12-09 17:37:36 UTC CC jhenner
errata-xmlrpc 2013-12-09 21:21:30 UTC Status MODIFIED ON_QA
Bruce Reeler 2013-12-10 00:31:08 UTC CC breeler, vpopovic
Flags needinfo?(vpopovic)
Flavio Percoco 2013-12-10 09:21:23 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?(vpopovic)
Don Domingo 2013-12-11 06:44:11 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 the Nova service.

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:41 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 the Nova service.

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

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.
Dave Allan 2013-12-16 16:38:21 UTC QA Contact ajeain jruzicka
Scott Lewis 2013-12-19 14:38:09 UTC CC sclewis
Scott Lewis 2013-12-19 14:38:42 UTC Blocks 1045065
Scott Lewis 2013-12-19 14:47:31 UTC Keywords TestOnly
errata-xmlrpc 2013-12-19 17:43:46 UTC Status ON_QA RELEASE_PENDING
errata-xmlrpc 2013-12-20 00:41:12 UTC Status RELEASE_PENDING CLOSED
Resolution --- ERRATA
Last Closed 2013-12-19 19:41:12 UTC
Perry Myers 2016-04-26 13:47:12 UTC CC pmyers
Russell Bryant 2019-09-09 14:40:22 UTC CC rbryant

Back to bug 1038638