yahoo-eng-team team mailing list archive

[OpenStack Infra <1810025@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://review.openstack.org/627779
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=58de79a58bfeda46c6ab7fcaa765b8a557652874
Submitter: Zuul
Branch:    master

commit 58de79a58bfeda46c6ab7fcaa765b8a557652874
Author: liuchengqian90 <xieling1990.happy@xxxxxxx>
Date:   Sat Dec 29 21:39:43 2018 +0800

    Clear residual qos rules after l2-agent restarts.
    
    During the l2-agent stop, if the policy rule is cleared,
    after the l2-agent is started, the qos rule that has been applied should be cleared.
    
    Change-Id: Iaaff10dfa8ac6ab8c9dead3124e2bb3caa03a665
    Closes-Bug: #1810025


** 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/1810025

Title:
  L2 agent do not clear QoS rules after restart

Status in neutron:
  Fix Released

Bug description:
  I runned a test about qos(driver=openvswitch) based rocky and found
  the following problems.

  1. craete a vm and found its port ,eg port_id= PORT_ID_A  .
  2. create a policy(eg , id=POLICY_ID) and create bandwidth_limit_rule (max_kbps=50000).
  3. update port PORT_ID_A with qos_policy POLICY_ID.
  4. 'ovs-vsctl list interface PORT_ID_A' to ensure its correct.

  Everything was working fine, so we continue

  5. stop neutron-openvswitch-agent 
  6. delete bandwidth_limit_rule in qos_policy POLICY_ID.
  7. start neutron-openvswitch-agent  
  8. 'ovs-vsctl list interface PORT_ID_A' again , 
     I found 'ingress_policing_rate' and 'ingress_policing_burst' were not changed. 
     That was not what I wanted.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1810025/+subscriptions