[OVN] OVN mech driver does not map new segments
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Fix Released
|
Medium
|
Rodolfo Alonso |
Bug Description
Related LP bug: https:/
Related bugzilla: https:/
This bug is related to OVN backend. "segments" service plugin must be enabled.
When a new segment is created (for example when a network is created), if this segment is associated to a physnet (flat and vlan type networks) and there is an L2 agent is running on a host with this physnet, a new "SegmentHostMap
In OVN the physnet <-> host mapping is done using the OVS DB [1]:
$ ovs-vsctl set open . external-
When an OVS DB is updated, the corresponding OVN SB chassis register is updated. This event is captured in Neutron. Neutron retrieves the current segments associated to the configured physnets (in the example "provider") and filters by network type (flat and vlan only). If any of those segments has no "SegmentHostMap
However when a new segment is created, OVN mech driver does not correctly check if this segment is located in an agent [2]. Because OVN mech driver has no "agent_type", this method never maps the new created segment with a host.
As reported in the bugzilla #2013820, OVN can be deployed with DHCP agents (for baremetal servers with Ironic). When a new network (and the corresponding segment) is created and a new subnet is added to this network, the DHCP agent receives this update. But Neutron server [3] reports this subnet as "non_local_subnets" because there is no mapping between this segment and the DHCP host. Because of this, the DHCP deletes/do not create the DHCP namespace and the DHCP port.
[1]https:/
[2]https:/
[3]https:/
Changed in neutron: | |
assignee: | nobody → Rodolfo Alonso (rodolfo-alonso-hernandez) |
tags: | added: ovn |
Changed in neutron: | |
importance: | Undecided → Medium |
Fix proposed to branch: master /review. opendev. org/c/openstack /neutron/ +/816856
Review: https:/