Comment 7 for bug 1726732

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

commit ee423e1fa035146904eb8cdd78660cf1cafa64e8
Author: Zachary <mazengxie@126.com>
Date: Fri Oct 27 10:13:58 2017 +0800

    [Qos] Fix residues of ovs in ingress bw limit

    When we delete vm port with attached QoS policy,
    it is just doing nothing if vif_port does not exist.

    This is fine for egress bandwidth limit as it is configured
    directly on vif_port in OVS.

    For ingress bw limit however it uses additional records in
    Openvswitch database: qos and queue. Those records are not
    cleaned up in such case.

    This patch also records port in self.ports in the case of
    bandwidth limit rules, just as in the case of dscp rules.
    Never execute port clear if vif_port not exists. Finally, ovs
    driver can clean such qos and queue records

    Change-Id: Iddeb49e1e6538a178ca468df0fdf9e0617ca4f1c
    Closes-Bug: #1726732