yahoo-eng-team team mailing list archive

[Maximilian Stinsky <2006145@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

Greetings,

While we tested a couple of disaster scenarios in our lab environment we
noticed that when we stop our rabbitmq cluster completely, the neutron
dynamic routing bgp speaker shuts down all bgp sessions to its peers.

This results in all announced floating ip's or subnet pools to go
offline.

We are running neutron wallaby (18.5.0) with the StaticScheduler for the
neutron bgp part.

In my opinion the bgp speaker should continue to announce its local cached state until the rabbitmq connection can be reestablished.
As most rabbitmq upgrades require a full downtime, upgrades to rabbitmq are almost impossible to do without openstack to be offline when using neutron dynamic routing.

** Affects: neutron
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/2006145

Title:
  BGP Speaker peer sessions down when rabbitmq offline

Status in neutron:
  New

Bug description:
  Greetings,

  While we tested a couple of disaster scenarios in our lab environment
  we noticed that when we stop our rabbitmq cluster completely, the
  neutron dynamic routing bgp speaker shuts down all bgp sessions to its
  peers.

  This results in all announced floating ip's or subnet pools to go
  offline.

  We are running neutron wallaby (18.5.0) with the StaticScheduler for
  the neutron bgp part.

  In my opinion the bgp speaker should continue to announce its local cached state until the rabbitmq connection can be reestablished.
  As most rabbitmq upgrades require a full downtime, upgrades to rabbitmq are almost impossible to do without openstack to be offline when using neutron dynamic routing.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/2006145/+subscriptions