Description of problem: When policy is created and attached to the network before VM is up (before port is active), it is not applied (no qos object in ovn nb db) Version-Release number of selected component (if applicable): puddle RHOS-16.1-RHEL-8-20210216.n.1 How reproducible: 100% Steps to Reproduce: 1. Make sure you are using an environment with qos enabled 2. Create a network, create a qos policy and apply to the network, example commands openstack network qos policy create bw-limiter openstack network qos rule create --type bandwidth-limit --max-kbps 3000 --max-burst-kbits 2400 --egress bw-limiter openstack network set --qos-policy bw-limiter 3. Launch 2 VMs on that network, wait until ports are ACTIVE then login to controller node and run 'ovn-nbctl list qos' Actual results: no qos objects in 'ovn-nbctl list qos' output - BUG qos rule does not work Expected results: qos objects listed in 'ovn-nbctl list qos' output. qos rules work Additional info: Note: I tried to launch RHEL VMs and ran iperf3 between the VMs (there was also security group allowing iperf traffic). The qos rule was not applied. After I re-applied the rule after VMs are up, all worked as expected.
Verified on RHOS-16.1-RHEL-8-20210413.n.0 which is using python3-networking-ovn-7.3.1-1.20210409093428.4e24f4c.el8ost.noarch Verified that the problem does not happen. When we first create a qos policy and attach it to a network, and only then we create a VM, the policy is working properly for the VM.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Red Hat OpenStack Platform 16.1.6 bug fix and enhancement advisory), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2021:2097