yahoo-eng-team team mailing list archive

[Balazs Gibizer <1915856@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

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://paste.openstack.org/show/802704/

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

** Affects: neutron
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1915856

Title:
  updating a qos policy on a bound port  from None to a policy with
  min_bw rules does not update placement allocation

Status in neutron:
  New

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://paste.openstack.org/show/802704/

  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

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1915856/+subscriptions