Neutron agent ports are added to br-int without any tag. That makes them trunk ports (receiving traffic for all VLANs) until neutron-openvswitch-agent will handle them.
Sometimes the ports are left untagged forever, meaning that for example ha-router ha port will send and receive traffic directly on the external network (jumps to br-int to br-ex , and also back), or dnsmasq starts handling dhcp requests on the external network.
Vague details here (it's all we have so far):
This also becomes an issue (still under investigation) with the ovs-vswitchd agent and the revalidator thread (the thread that will check the kernel datapath flows under some circumstances to get stuck, for some reason it slows down a lot while analyzing trunk ports, eventually crashing the node on CPU usage).
Neutron agent ports are added to br-int without any tag. That makes them trunk ports (receiving traffic for all VLANs) until neutron- openvswitch- agent will handle them.
Sometimes the ports are left untagged forever, meaning that for example ha-router ha port will send and receive traffic directly on the external network (jumps to br-int to br-ex , and also back), or dnsmasq starts handling dhcp requests on the external network.
Vague details here (it's all we have so far):
This also becomes an issue (still under investigation) with the ovs-vswitchd agent and the revalidator thread (the thread that will check the kernel datapath flows under some circumstances to get stuck, for some reason it slows down a lot while analyzing trunk ports, eventually crashing the node on CPU usage).
This is also related to one security lp here: https:/ /bugs.launchpad .net/bugs/ 1734320