[qos]set running vms ingress-bandwidth-limit, then delete running vm,but ovs queue is still residual
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Fix Released
|
Medium
|
Zachary Ma |
Bug Description
1.create vm:
[root@172e18e211e96 ~]# nova interface-list mzx4
+------
| Port State | Port ID | Net ID | IP addresses | MAC Addr |
+------
| ACTIVE | f4ae0545-
+------
2. Set the policy on the port.
[root@172e18e211e96 ~]# openstack port set --qos-policy bw-limiter f4ae0545-
and check ovs by cmd:
[root@172e18e211e9 ~]# ovs-vsctl list queue
_uuid : 1e4f2c2d-
dscp : []
external_ids : {id="tapf4ae054
other_config : {burst="10000000", max-rate=
3.then delete vm in running status,and check ovs again:
[root@172e18e211e9 ~]# ovs-vsctl list queue
_uuid : 1e4f2c2d-
dscp : []
external_ids : {id="tapf4ae054
other_config : {burst="10000000", max-rate=
tapf4ae0545-ca has been removed in ovs, but ovs queue is still residual!!
summary: |
- [qos]configure running vms ingress-bandwidth-limit, then delete running - vm,but ovs queue is still residual + [qos]set running vms ingress-bandwidth-limit, then delete running vm,but + ovs queue is still residual |
Changed in neutron: | |
assignee: | nobody → Slawek Kaplonski (slaweq) |
Changed in neutron: | |
assignee: | Zachary Ma (mazengxie) → Slawek Kaplonski (slaweq) |
Changed in neutron: | |
assignee: | Slawek Kaplonski (slaweq) → Zachary Ma (mazengxie) |
I can confirm that both qos and queue is not removed from ovs in such case