This also happen if you are using "DVR", the packets will not go through tunnelling, hence not hitting the queue core ovn configures on the tunnel interfaces.
Yeah, you won't see Queue entries in ovs, they are created directly on the kernel. But they work when it's compute to compute through tunnelling (we have tests running that and they pass, although, as soon as you try to run those tests with DVR, or by using vlan tenant networks, it stops working.
This also happen if you are using "DVR", the packets will not go through tunnelling, hence not hitting the queue core ovn configures on the tunnel interfaces.
I opened this bug:
https:/ /github. com/openvswitch /ovs-issues/ issues/ 150
Yeah, you won't see Queue entries in ovs, they are created directly on the kernel. But they work when it's compute to compute through tunnelling (we have tests running that and they pass, although, as soon as you try to run those tests with DVR, or by using vlan tenant networks, it stops working.