yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #51411
[Bug 1515533] Re: QoS policy is not enforced when using a previously used port
Reviewed: https://review.openstack.org/317655
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=bc47fe97d3bf6322facca58f0f1b8081c386ffe9
Submitter: Jenkins
Branch: master
commit bc47fe97d3bf6322facca58f0f1b8081c386ffe9
Author: Ilya Chukhnakov <ichukhnakov@xxxxxxxxxxxx>
Date: Tue May 17 19:54:29 2016 +0300
Call ext_manager.delete_port on port removal
This patch updates OVSNeutronAgent to call ext_manager.delete_port
when the port is removed (similar to how CommonAgentLoop does).
Otherwise the QoS PortPolicyMap is not properly updated on port
removal and QoS extension will not apply policies if that port is
later reused by a VM on the same node (unless the agent is restarted).
Change-Id: I306c496985a550176d0ddc6eb33a4a4d351acb55
Closes-Bug: #1515533
** 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/1515533
Title:
QoS policy is not enforced when using a previously used port
Status in neutron:
Fix Released
Bug description:
When using a port with a QoS policy that was already used the policy
is not enforced
Version
=======
CentOS 7.1 RDO Liberty
openstack-neutron-7.0.1-dev28.el7.centos.noarch
openstack-neutron-common-7.0.1-dev28.el7.centos.noarch
python-neutron-7.0.1-dev28.el7.centos.noarch
openstack-neutron-ml2-7.0.1-dev28.el7.centos.noarch
openstack-neutron-openvswitch-7.0.1-dev28.el7.centos.noarch
How to reproduce
================
1. Create a QoS policy
2. Create a QoS bandwidth rule
3. Create a port
4. Associate the port with a policy
5. Launch the instance with the above port attached
6. Verify the policy is enforced
7. Delete the instance
8. Launch an instance with the above port attached
9. Verify that the QoS policy is not enforced
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1515533/+subscriptions
References