Public bug reported:
1.create vm:
[root@172e18e211e96 ~]# nova interface-list mzx4
+------------+--------------------------------------+--------------------------------------+--------------+-------------------+
| Port State | Port ID | Net ID
| IP addresses | MAC Addr |
+------------+--------------------------------------+--------------------------------------+--------------+-------------------+
| ACTIVE | f4ae0545-ca86-40c5-b2f7-064e521f13db |
1464fb8c-3879-4e2a-9833-3aa0882285d5 | 5.5.5.11 | fa:16:3e:57:cb:ba |
+------------+--------------------------------------+--------------------------------------+--------------+-------------------+
2. Set the policy on the port.
[root@172e18e211e96 ~]# openstack port set --qos-policy bw-limiter
f4ae0545-ca86-40c5-b2f7-064e521f13db
and check ovs by cmd：
[root@172e18e211e9 ~]# ovs-vsctl list queue
_uuid : 1e4f2c2d-4116-4484-8eb6-5b13d9de649f
dscp : []
external_ids : {id="tapf4ae0545-ca", queue_type="0"}
other_config : {burst="10000000", max-rate="100000000"}
3.then delete vm in running status,and check ovs again:
[root@172e18e211e9 ~]# ovs-vsctl list queue
_uuid : 1e4f2c2d-4116-4484-8eb6-5b13d9de649f
dscp : []
external_ids : {id="tapf4ae0545-ca", queue_type="0"}
other_config : {burst="10000000", max-rate="100000000"}
tapf4ae0545-ca has been removed in ovs, but ovs queue is still
residual!!
** Affects: neutron
Importance: Undecided
Status: New
** Tags: qos
** Summary changed:
- [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
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1726732
Title:
[qos]set running vms ingress-bandwidth-limit, then delete running
vm,but ovs queue is still residual
Status in neutron:
New
Bug description:
1.create vm:
[root@172e18e211e96 ~]# nova interface-list mzx4
+------------+--------------------------------------+--------------------------------------+--------------+-------------------+
| Port State | Port ID | Net ID
| IP addresses | MAC Addr |
+------------+--------------------------------------+--------------------------------------+--------------+-------------------+
| ACTIVE | f4ae0545-ca86-40c5-b2f7-064e521f13db |
1464fb8c-3879-4e2a-9833-3aa0882285d5 | 5.5.5.11 | fa:16:3e:57:cb:ba |
+------------+--------------------------------------+--------------------------------------+--------------+-------------------+
2. Set the policy on the port.
[root@172e18e211e96 ~]# openstack port set --qos-policy bw-limiter
f4ae0545-ca86-40c5-b2f7-064e521f13db
and check ovs by cmd：
[root@172e18e211e9 ~]# ovs-vsctl list queue
_uuid : 1e4f2c2d-4116-4484-8eb6-5b13d9de649f
dscp : []
external_ids : {id="tapf4ae0545-ca", queue_type="0"}
other_config : {burst="10000000", max-rate="100000000"}
3.then delete vm in running status,and check ovs again:
[root@172e18e211e9 ~]# ovs-vsctl list queue
_uuid : 1e4f2c2d-4116-4484-8eb6-5b13d9de649f
dscp : []
external_ids : {id="tapf4ae0545-ca", queue_type="0"}
other_config : {burst="10000000", max-rate="100000000"}
tapf4ae0545-ca has been removed in ovs, but ovs queue is still
residual!!
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1726732/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
