Qos rules not cleaned by L2 agent
Bug #1663908 reported by
Slawek Kaplonski
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Fix Released
|
Undecided
|
David Shaughnessy |
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
Changed in neutron: | |
assignee: | nobody → David Shaughnessy (david-shaughnessy) |
To post a comment you must log in.
Changing a qos policy for a port has no problem. But clean is true.