Qos rules not cleaned by L2 agent

Bug #1663908 reported by Slawek Kaplonski
6
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)
Revision history for this message
Lv Jiawei (zhangoic) wrote :

Changing a qos policy for a port has no problem. But clean is true.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to neutron (master)

Fix proposed to branch: master
Review: https://review.openstack.org/449710

Changed in neutron:
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to neutron (master)

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 address hidden>
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
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/neutron 11.0.0.0b1

This issue was fixed in the openstack/neutron 11.0.0.0b1 development milestone.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to neutron (stable/ocata)

Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/462937

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to neutron (stable/ocata)

Reviewed: https://review.openstack.org/462937
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=8431ac7b93c15b0be4f9ce9e0584d35a78966adf
Submitter: Jenkins
Branch: stable/ocata

commit 8431ac7b93c15b0be4f9ce9e0584d35a78966adf
Author: David Shaughnessy <email address hidden>
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
    (cherry picked from commit 21359e29ae38bd644709cd712b7cb5fbf1bd55b4)

tags: added: in-stable-ocata
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/neutron 10.0.2

This issue was fixed in the openstack/neutron 10.0.2 release.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.