yahoo-eng-team team mailing list archive

[Lajos Katona <1894825@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

update_qos_minbw_allocation (see: https://opendev.org/openstack/neutron-lib/src/commit/245e005d1bbb9af5e57ff600fb97b2a13c85c83b/neutron_lib/placement/client.py ) assumes that placement allocation records can be updated by 0 (like: 
{
  "allocations": {
    "4e061c03-611e-4caa-bf26-999dcff4284e": {
      "resources": {
        "NET_BW_EGR_KILOBIT_PER_SEC": 0
      }
    }
}

), 
but that is not possible now, the way to do this is to delete the resource class,
see the storyboard story for this:
https://storyboard.openstack.org/#!/story/2008111

** Affects: neutron
     Importance: Undecided
     Assignee: Lajos Katona (lajos-katona)
         Status: New


** Tags: placement 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/1894825

Title:
  placement allocation update accepts only integers from 1

Status in neutron:
  New

Bug description:
  update_qos_minbw_allocation (see: https://opendev.org/openstack/neutron-lib/src/commit/245e005d1bbb9af5e57ff600fb97b2a13c85c83b/neutron_lib/placement/client.py ) assumes that placement allocation records can be updated by 0 (like: 
  {
    "allocations": {
      "4e061c03-611e-4caa-bf26-999dcff4284e": {
        "resources": {
          "NET_BW_EGR_KILOBIT_PER_SEC": 0
        }
      }
  }

  ), 
  but that is not possible now, the way to do this is to delete the resource class,
  see the storyboard story for this:
  https://storyboard.openstack.org/#!/story/2008111

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