[Segments] Network isn't scheduled to the dhcp agent in new segment when segment is added after subnet creation
Bug #1917811 reported by
Slawek Kaplonski
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
New
|
Medium
|
Slawek Kaplonski |
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.
Changed in neutron: | |
importance: | Undecided → Medium |
assignee: | nobody → Slawek Kaplonski (slaweq) |
tags: | added: segments |
To post a comment you must log in.
Patch: https:/ /review. opendev. org/c/openstack /neutron/ +/778784