L2 agent do not clear QoS rules after restart

[Chengqian Liu]

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.

[Slawek Kaplonski (slaweq)]

Hi Chengqian Liu,

Thx for report this bug. Can You explain what is "CN" in bug title?
Also, I see that You assigned this bug to Your self, are You working on fix for it currently?

[Chengqian Liu (liuchengqian90)]

Hi Slawek:
CN means "compute node" in bug title and this is the code review:
https://review.openstack.org/#/c/627779/

[Slawek Kaplonski (slaweq)]

Ok, thx for explanation and link to patch.
I think that this issue is not related only to neutron-openvswitch-agent but to all L2 agents. Am I right?

[Chengqian Liu (liuchengqian90)]

Yes.
But I only tested it with openvswitch as the driver.

[OpenStack Infra (hudson-openstack)]

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 <[e-mail]>
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

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/632458

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/632458
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=e04ee2c5b66af84f27cc2f1fa0ce3f92fe5676e9
Submitter: Zuul
Branch: stable/rocky

commit e04ee2c5b66af84f27cc2f1fa0ce3f92fe5676e9
Author: liuchengqian90 <[e-mail]>
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
    (cherry picked from commit 58de79a58bfeda46c6ab7fcaa765b8a557652874)

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: stable/queens
Review: https://review.openstack.org/632936

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/632936
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=81d51ae876f4b163472de8f24a3ec1d1d7ac2078
Submitter: Zuul
Branch: stable/queens

commit 81d51ae876f4b163472de8f24a3ec1d1d7ac2078
Author: liuchengqian90 <[e-mail]>
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
    (cherry picked from commit 58de79a58bfeda46c6ab7fcaa765b8a557652874)
    (cherry picked from commit e04ee2c5b66af84f27cc2f1fa0ce3f92fe5676e9)

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/neutron 14.0.0.0b2 development milestone.

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

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