Back to bug 1036523

Who When What Removed Added
Mark McLoughlin 2013-12-02 09:11:07 UTC CC markmc
RHEL Program Management 2013-12-02 12:17:07 UTC Target Release --- 4.0
lpeer 2013-12-02 18:09:17 UTC Status NEW ASSIGNED
CC lpeer
Assignee rhos-maint mnewby
Perry Myers 2013-12-05 14:44:38 UTC Priority unspecified high
Target Milestone --- async
Maru Newby 2013-12-11 06:30:47 UTC Flags needinfo?(markmc)
Maru Newby 2013-12-11 06:34:11 UTC CC fdinitto
Flags needinfo?(fdinitto)
Fabio Massimo Di Nitto 2013-12-11 08:38:27 UTC Flags needinfo?(markmc) needinfo?(fdinitto)
Mark McLoughlin 2013-12-11 18:27:13 UTC CC fpercoco, gsim, rbryant
Scott Lewis 2013-12-13 18:16:26 UTC Keywords ZStream
lpeer 2013-12-15 11:42:39 UTC Whiteboard mid-feb
Perry Myers 2013-12-15 12:37:11 UTC Whiteboard mid-feb
Perry Myers 2013-12-15 12:48:35 UTC Flags needinfo?(gsim)
Perry Myers 2013-12-15 12:48:52 UTC CC kgiusti
Flags needinfo?(kgiusti)
Gordon Sim 2013-12-16 12:01:25 UTC Flags needinfo?(gsim) needinfo?(kgiusti)
Maru Newby 2013-12-17 06:33:06 UTC Link ID Launchpad 1261631
Maru Newby 2013-12-17 06:46:53 UTC Flags needinfo?(gsim)
Gordon Sim 2013-12-17 11:27:09 UTC Flags needinfo?(gsim)
Perry Myers 2014-01-06 18:37:24 UTC Whiteboard mid-Feb
Scott Lewis 2014-01-08 19:58:33 UTC Target Milestone async A2
Scott Lewis 2014-01-08 20:00:55 UTC Whiteboard mid-Feb
John Skeoch 2014-01-13 01:08:21 UTC CC hateya
lpeer 2014-01-15 11:50:49 UTC Assignee mnewby ihrachys
lpeer 2014-02-10 09:13:22 UTC Target Milestone A2 A3
Ihar Hrachyshka 2014-02-10 09:18:20 UTC Link ID OpenStack gerrit 67450
Ihar Hrachyshka 2014-02-10 09:18:42 UTC Link ID OpenStack gerrit 67449
Ihar Hrachyshka 2014-02-10 09:32:39 UTC Link ID OpenStack gerrit 68958
Ihar Hrachyshka 2014-02-10 09:33:04 UTC Link ID OpenStack gerrit 68959
lpeer 2014-03-03 15:53:53 UTC Target Milestone A3 A4
Nir Yechiel 2014-03-25 17:12:37 UTC Blocks 1080561
Ihar Hrachyshka 2014-03-26 14:23:53 UTC Link ID OpenStack gerrit 81261
Ihar Hrachyshka 2014-03-28 13:07:51 UTC Status ASSIGNED POST
Ihar Hrachyshka 2014-03-31 15:10:18 UTC Blocks 1082661
Ihar Hrachyshka 2014-03-31 15:15:10 UTC Blocks 1082664
Ihar Hrachyshka 2014-03-31 15:16:33 UTC Blocks 1082665
Ihar Hrachyshka 2014-03-31 15:17:22 UTC Blocks 1082666
Ihar Hrachyshka 2014-03-31 15:18:07 UTC Blocks 1082668
Ihar Hrachyshka 2014-03-31 15:18:46 UTC Blocks 1082669
Ihar Hrachyshka 2014-03-31 15:19:26 UTC Blocks 1082670
Ihar Hrachyshka 2014-03-31 15:20:03 UTC Blocks 1082672
Ihar Hrachyshka 2014-04-01 09:31:23 UTC Keywords Rebase
Red Hat Bugzilla 2014-04-01 09:31:23 UTC Doc Type Bug Fix Rebase: Bug Fixes and Enhancements
Ihar Hrachyshka 2014-04-01 12:05:12 UTC Assignee ihrachys twilson
lpeer 2014-04-01 16:11:14 UTC Assignee twilson ihrachys
Ofer Blaut 2014-04-06 06:22:27 UTC QA Contact oblaut yfried
Ofer Blaut 2014-04-06 06:23:18 UTC Keywords OtherQA
CC oblaut
Shai Revivo 2014-04-12 07:00:25 UTC CC srevivo
Miguel Angel Ajo 2014-04-14 08:22:41 UTC Status POST MODIFIED
CC majopela
Fixed In Version openstack-neutron-2013.2.3-4.el6ost
Miguel Angel Ajo 2014-04-14 10:52:48 UTC Doc Text Cause:

If we had a list of message brokers, we would not try to reconnect to the next one in the list in case of a failed connection.

Consequence:

The service keeps trying to reconnect to the same broken message broker, even if there are several hosts configured.

Fix:

This change makes reconnect() implementation to select the next broker in the list.

Result:
When several broker hosts are provided, it will try the next one in the list at every connection attempt.

This also means that non-failure reconnect attempts will also switch the
current broker. All in all, users should not rely on any particular order to
use brokers from the list, so this should not constitute an issue.
Doc Type Rebase: Bug Fixes and Enhancements Bug Fix
errata-xmlrpc 2014-04-14 21:07:26 UTC Status MODIFIED ON_QA
Bruce Reeler 2014-05-19 03:27:23 UTC CC breeler
Doc Text Cause:

If we had a list of message brokers, we would not try to reconnect to the next one in the list in case of a failed connection.

Consequence:

The service keeps trying to reconnect to the same broken message broker, even if there are several hosts configured.

Fix:

This change makes reconnect() implementation to select the next broker in the list.

Result:
When several broker hosts are provided, it will try the next one in the list at every connection attempt.

This also means that non-failure reconnect attempts will also switch the
current broker. All in all, users should not rely on any particular order to
use brokers from the list, so this should not constitute an issue.
Cause: Without a list of message brokers, openstack-neutron keeps trying to reconnect when there is a failed connection.

Consequence: The service keeps trying to reconnect to the same broken message broker, even if there are several hosts configured.

Fix: This change makes the reconnect() implementation to select the next broker in the list.

Result: When several broker hosts are provided, it will try the next one in the list at every connection attempt.

This means that non-failure reconnect attempts will also switch the current broker. Generally, users should not rely on any particular order when using brokers from the list, so this fix should not cause a problem.
errata-xmlrpc 2014-05-29 15:00:21 UTC Status ON_QA RELEASE_PENDING
errata-xmlrpc 2014-05-29 20:17:44 UTC Status RELEASE_PENDING CLOSED
Resolution --- ERRATA
Last Closed 2014-05-29 16:17:44 UTC
Nejc Saje 2014-07-25 13:04:50 UTC Blocks 1123376
Perry Myers 2016-04-26 19:52:00 UTC CC pmyers
Russell Bryant 2019-09-09 15:35:43 UTC CC rbryant

Back to bug 1036523