Public bug reported:
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
** Affects: neutron
Importance: Undecided
Status: New
** Tags: qos
--
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:
New
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 : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
