updating a qos policy on a bound port from None to a policy with min_bw rules does not update placement allocation
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Fix Released
|
Medium
|
Przemyslaw Szczerbik |
Bug Description
1) create a port without qos policy (and also the net has no qos policy)
2) boot a server with the port
3) set the the qos policy of the port for a policy with min_bw rules
Expected:
* port update is rejected as neutron does not know which resource provider the bandwidth needs to be allocated
Actual:
* port update accepted the resource request of the port is updated according to the new policy but placement allocation does not created
Reproduction with printouts: http://
A variant of the bug:
1) create a port with qos policy
2) boot a server with that port
3) update the port qos policy to None (note it is only possible with the REST API, the CLI client does not support $openstack port set --no-qos-policy)
4) update the qos policy of the port from None to an existing qos policy
Expected:
* same as above
Actual:
* same as above
Changed in neutron: | |
assignee: | nobody → Lajos Katona (lajos-katona) |
Changed in neutron: | |
status: | New → Confirmed |
importance: | Undecided → Medium |
tags: | added: qos |
Changed in neutron: | |
assignee: | Lajos Katona (lajos-katona) → Przemyslaw Szczerbik (pszczerbik) |
Changed in neutron: | |
status: | Fix Committed → Fix Released |
An extra note at step 3) in the reproduction the allocation key of the port binding still points to the same RP as after step 2) even if the allocation from the RP is properly removed. See printouts in http:// paste.openstack .org/show/ 802717/