Reviewed: https://review.openstack.org/449710 Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=21359e29ae38bd644709cd712b7cb5fbf1bd55b4 Submitter: Jenkins Branch: master
commit 21359e29ae38bd644709cd712b7cb5fbf1bd55b4 Author: David Shaughnessy <[email protected]> Date: Fri Mar 24 15:51:11 2017 +0000 Clear QoS rules from ports without a qos policy. This patch addresses a bug where ports that had their QoS policy removed did not have the rules deleted as the agent was restarting and cleared the internal port info. This results in the policy still being in effect while it has been cleared from the port qos-policy field. Change-Id: I2e8e4aa96d2fd15b344220c4bf8a4713197fae4e Closes-Bug: 1663908 ** 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/1663908 Title: Qos rules not cleaned by L2 agent Status in neutron: Fix Released Bug description: If QoS policy is removed from port when L2 agent is down, then it is not removed after agent is up again. Such qos bandwidth limit rule is still configured on port on L2 agent side (I tested ovs). How to reproduce: * Apply QoS policy with bandwidth limit rule to port * Disable L2 agent * Remove QoS policy from port * Start L2 agent * Bandwidth limit will not be removed from interface in ovs To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1663908/+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
