Bug 1951170

Description of problem:
This bug is similar to BZ1936527. The issue was resolved for qos policies associated to sriov ports, but it fails when the policy is associated to a network instead.

When a QoS policy with an egress BW limit rule is assigned to a network, if an SRIOV port has been created for that network (type direct or macvtap), the corresponding rule should be managed by the sriov agent and should not be added to the OVN NBDB's QoS table.

However, the entry on the QoS table is created for that port, which is wrong.

The bw limit rule is also assigned by the sriov agent, which is correct. The bw limit is correctly applied to the traffic.






Version-Release number of selected component (if applicable):
RHOS-16.1-RHEL-8-20210415.n.0

How reproducible:
100%


Steps to Reproduce:
1) create qos policy with an egress bw limit rule and assing it to an network:
openstack network qos policy create p0
openstack network qos rule create p0 --type bandwidth-limit --max-kbps 500000000 --max-burst-kbits 40000000
openstack network set --qos-policy p0 public
2) check qos ovn nbdb table
podman exec ovn_controller ovn-nbctl --db=tcp:10.20.1.73:6641 list qos | grep -C5 0917ed75-6362-4522-a468-c3a8c89712fd
_uuid               : c2758e23-195e-4efa-8f9f-c057955ba6c3
action              : {}
bandwidth           : {burst=40000000, rate=540000}
direction           : from-lport
external_ids        : {}
match               : "inport == \"0917ed75-6362-4522-a468-c3a8c89712fd\""
priority            : 2002