Description of problem: When setting a qos policy to an existing port a new qos entry in not created in NBDB qos table. Version-Release number of selected component (if applicable): 16.0-RHEL-8/RHOS_TRUNK-16.0-RHEL-8-20200406.n.1 python3-networking-ovn-7.1.1-0.20200403214619.4114bc5.el8ost.noarch How reproducible: 100% Steps to Reproduce: 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 create internal_A openstack port create vm1-port --network internal_A openstack port set --qos-policy bw-limiter <PORT ID> On a node with OVN controller run 'ovn-nbctl qos-list <logical switch uuid of internal_A network>' Actual results: qos entry was not added to NBDB Expected results: qos entry added to NBDB Additional info: Note, in case I create one more port with qos policy the entry is created along with the new ove (of the second port)
Probably need to be retested after https://review.opendev.org/#/c/711317/ is applied
One more related patch https://review.opendev.org/#/c/707352/
Verified that the issue does not happen on RHOS-16.1-RHEL-8-20200625.n.0 with python3-networking-ovn-7.2.1-0.20200611111150.18fabca.el8ost.noarch
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, 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-2020:3148