Back to bug 1038711
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Perry Myers | 2013-12-05 16:35:40 UTC | Assignee | rhos-maint | lpeer |
| Perry Myers | 2013-12-05 16:36:35 UTC | Depends On | 1038638 | |
| Perry Myers | 2013-12-05 16:36:36 UTC | See Also | https://bugzilla.redhat.com/show_bug.cgi?id=1038638 | |
| Flavio Percoco | 2013-12-06 14:55:10 UTC | Status | NEW | POST |
| CC | fpercoco | |||
| Perry Myers | 2013-12-09 15:12:27 UTC | Assignee | lpeer | twilson |
| Terry Wilson | 2013-12-09 19:27:49 UTC | Status | POST | MODIFIED |
| Fixed In Version | openstack-neutron-2013.2-14.el6ost | |||
| Ofer Blaut | 2013-12-09 20:27:55 UTC | Keywords | OtherQA | |
| errata-xmlrpc | 2013-12-09 21:22:44 UTC | Status | MODIFIED | ON_QA |
| Bruce Reeler | 2013-12-10 00:25:33 UTC | CC | breeler | |
| Flags | needinfo?(fpercoco) | |||
| Flavio Percoco | 2013-12-10 09:21:30 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?(fpercoco) | |||
| Don Domingo | 2013-12-11 06:37:48 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 Neutron. 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:22 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 Neutron. 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. Neutron). 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. |
| lpeer | 2013-12-11 18:22:11 UTC | CC | lpeer | |
| QA Contact | oblaut | ihrachys | ||
| Ihar Hrachyshka | 2013-12-17 17:00:07 UTC | CC | oblaut | |
| Flags | needinfo?(oblaut) | |||
| Ihar Hrachyshka | 2013-12-17 17:32:42 UTC | Status | ON_QA | VERIFIED |
| Ofer Blaut | 2013-12-17 19:47:46 UTC | Flags | needinfo?(oblaut) | |
| errata-xmlrpc | 2013-12-19 17:44:11 UTC | Status | VERIFIED | RELEASE_PENDING |
| errata-xmlrpc | 2013-12-20 00:41:23 UTC | Status | RELEASE_PENDING | CLOSED |
| Resolution | --- | ERRATA | ||
| Last Closed | 2013-12-19 19:41:23 UTC | |||
| Perry Myers | 2016-04-26 21:51:46 UTC | CC | pmyers | |
| Russell Bryant | 2019-09-09 13:58:15 UTC | CC | rbryant |
Back to bug 1038711