yahoo-eng-team team mailing list archive

[Jakub Darmach <2125482@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

In example use case we have two network scopes, with two separated BGP
speakers to be scheduled amongst i.e. 4 controllers, using
StaticScheduler for troubleshooting purposes.

Symptoms:
1. With BGP both speakers scheduled on all DR agents only the first scheduled will be picked up on BGP peers.
2. With BGP speakers scheduled on dragents separately (i.e. speaker1 on dragent 1 and 2, speaker2 on dragent 3 and 4) both speakers are visible as neighbours and routes advertised on BGP peers.

Looks lik second speaker scheduled on already populated dragent is
either not scheduled or not functioning.

** 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/2125482

Title:
  Subsequent BGP speaker scheduled onto dragent does not work

Status in neutron:
  New

Bug description:
  In example use case we have two network scopes, with two separated BGP
  speakers to be scheduled amongst i.e. 4 controllers, using
  StaticScheduler for troubleshooting purposes.

  Symptoms:
  1. With BGP both speakers scheduled on all DR agents only the first scheduled will be picked up on BGP peers.
  2. With BGP speakers scheduled on dragents separately (i.e. speaker1 on dragent 1 and 2, speaker2 on dragent 3 and 4) both speakers are visible as neighbours and routes advertised on BGP peers.

  Looks lik second speaker scheduled on already populated dragent is
  either not scheduled or not functioning.

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