Reviewed: https://review.opendev.org/740967 Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=ccbebfeaccf657caf8bcf8d635e3032e4c51c658 Submitter: Zuul Branch: master
commit ccbebfeaccf657caf8bcf8d635e3032e4c51c658 Author: Maciej Józefczyk <[email protected]> Date: Tue Jul 14 11:59:58 2020 +0000 [OVN] Fix logic issue while deleting port with QoS While port has QoS policy configured the policy wasn't deleted because of logic issue. Change-Id: I3d7e70a4a110c68a89d6c575abf121cd9b97e439 Closes-Bug: #1886962 ** Changed in: neutron Status: In Progress => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1886962 Title: [OVN][QOS] NBDB qos table entries still exist even after corresponding neutron ports are deleted Status in neutron: Fix Released Bug description: When removing neutron ports with qos policy applied, corresponding entries are not removed from NBDB qos table. 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 this stage 'ovn-nbctl list qos' displays corresponding qos rule of the port openstack port delete <PORT ID> Result: port removed from neutron DB - this is OK. But OVN NBDB qos table still displays qos entry for this port: To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1886962/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : [email protected] Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
