yahoo-eng-team team mailing list archive

[OpenStack Infra <1915849@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://review.opendev.org/c/openstack/neutron/+/815421
Committed: https://opendev.org/openstack/neutron/commit/18ec0eb20921e41ba4cade555f9da823c9dbfa13
Submitter: "Zuul (22348)"
Branch:    master

commit 18ec0eb20921e41ba4cade555f9da823c9dbfa13
Author: Przemyslaw Szczerbik <przemyslaw.szczerbik@xxxxxxxx>
Date:   Mon Oct 25 13:24:07 2021 +0200

    Fix placement allocation update for port with network QoS policy
    
    If port has no QoS policy on its own, fallback to the network
    QoS policy and use it to check if Placement allocation needs
    to be updated.
    
    Closes-Bug: #1915849
    Change-Id: Iffc87e4021391bcb98375621739a59064540a6a7


** 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/1915849

Title:
  setting the qos policy of a bound port in a network with default qos
  policy does not update placement allocation

Status in neutron:
  Fix Released

Bug description:
  1) have a net with a qos policy set
  2) create a port in that net without specific qos policy
  3) boot a server with that port
  4) set a specific qos policy on the port

  Expected:
  * The neutron port resource request is changed according to the new qos policy set on the port.
  * The resource allocation in placement is changed according to the new qos policy set on the port.

  Actual:
  * The neutron port resource request is changed according to the new qos policy. So this is OK.
  * But the allocation in placement still matches with the qos policy of the network not the qos policy of the port

  See reproduction steps with printouts from a fairly fresh devstack
  from master: http://paste.openstack.org/show/802701/

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