yahoo-eng-team team mailing list archive

[Slawek Kaplonski <1917811@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

How to reproduce the issue:

1. Create network and e.g. 2 segments in it (but don't turn on neutron-ovs-agents in one of the specific segments, so hosts which belongs to that segment aren't really known to the neutron server)
2. Network will not be scheduled in that "unknown" segment,
3. Turn on ovs agent, it will report that it's there and what bridge mappings it has,
4. Neutron should schedule network to additional dhcp agent(s) which are on the hosts connected to the new segment, but it will not happen.

If things are don't in opposite order (first segment is recorded in
neutron, next subnet is created) then network is scheduled to dhcp
agents properly.

** Affects: neutron
     Importance: Medium
     Assignee: Slawek Kaplonski (slaweq)
         Status: New


** Tags: segments

** Changed in: neutron
   Importance: Undecided => Medium

** Changed in: neutron
     Assignee: (unassigned) => Slawek Kaplonski (slaweq)

** Tags added: segments

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

Title:
  [Segments] Network isn't scheduled to the dhcp agent in new segment
  when segment is added after subnet creation

Status in neutron:
  New

Bug description:
  How to reproduce the issue:

  1. Create network and e.g. 2 segments in it (but don't turn on neutron-ovs-agents in one of the specific segments, so hosts which belongs to that segment aren't really known to the neutron server)
  2. Network will not be scheduled in that "unknown" segment,
  3. Turn on ovs agent, it will report that it's there and what bridge mappings it has,
  4. Neutron should schedule network to additional dhcp agent(s) which are on the hosts connected to the new segment, but it will not happen.

  If things are don't in opposite order (first segment is recorded in
  neutron, next subnet is created) then network is scheduled to dhcp
  agents properly.

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