yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #85178
[Bug 1915898] [NEW] changing the qos policy on a network does not change the placement allocation of the bound ports in the network
Public bug reported:
1) create a network with qos policy (with min_bw rule)
2) create a port in that network without explicit qos policy (so the port inherits the policy from the network)
3) boot a server with that port
4) update the qos policy on the network
Expected either:
A)
* qos policy change is accepted
* the port resource request is updated according to the new qos policy
* the placement allocation is updated according to the new qos policy
B)
* qos policy update is rejected
Actual:
* qos policy change is accepted -> OK as in A)
* the port resource request is updated according to the new qos policy -> OK as in A)
* the placement allocation is _not_ updated -> NOT OK in A)
See the specific reproduction steps with printouts in:
http://paste.openstack.org/show/802718/
** Affects: neutron
Importance: Undecided
Status: New
** Tags: qos
** Tags added: qos
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1915898
Title:
changing the qos policy on a network does not change the placement
allocation of the bound ports in the network
Status in neutron:
New
Bug description:
1) create a network with qos policy (with min_bw rule)
2) create a port in that network without explicit qos policy (so the port inherits the policy from the network)
3) boot a server with that port
4) update the qos policy on the network
Expected either:
A)
* qos policy change is accepted
* the port resource request is updated according to the new qos policy
* the placement allocation is updated according to the new qos policy
B)
* qos policy update is rejected
Actual:
* qos policy change is accepted -> OK as in A)
* the port resource request is updated according to the new qos policy -> OK as in A)
* the placement allocation is _not_ updated -> NOT OK in A)
See the specific reproduction steps with printouts in:
http://paste.openstack.org/show/802718/
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1915898/+subscriptions
Follow ups