yahoo-eng-team team mailing list archive

[OpenStack Infra <2101063@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://review.opendev.org/c/openstack/neutron/+/943664
Committed: https://opendev.org/openstack/neutron/commit/6d5366278551d62d0d44f9bfb400f8546e4b0d48
Submitter: "Zuul (22348)"
Branch:    master

commit 6d5366278551d62d0d44f9bfb400f8546e4b0d48
Author: Rodolfo Alonso Hernandez <ralonsoh@xxxxxxxxxx>
Date:   Tue Mar 4 16:05:10 2025 +0000

    [OVN] Do not call ``QoSAddCommand`` without max-bw/DSCP rule
    
    The ML2/OVN QoS extension formats the Neutron QoS rules into the
    corresponding QoS registers and LSP.options values. The OVN QoS
    registers allow to define filters for a specific traffic, matching
    the direction and the source port. This registers can have
    a "rate" and a "dscp" values defined. It is mandatory to at least
    define one of these parameters. If, for example, the Neutron rules
    only define a min-bw rule, none of these parameters will be set in
    the dictionary with the OVN QoS rules. In that case, ``qos_add`` is
    not called.
    
    Closes-Bug: #2101063
    Change-Id: Ia4f1d61753594c54f55bd146ad6dc06195a01485


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

Title:
  [OVN] min-bw QoS policy cannot be defined alone, exception raised

Status in neutron:
  Fix Released

Bug description:
  If a QoS policy with a single min-bw rule is set to a port bound to
  ML2/OVN, the mechanism driver (the QoS extension in particular) will
  throw an exception:
  https://paste.opendev.org/show/bu18X03XMk3eRUzeUiqC/

  Jira reference: https://issues.redhat.com/browse/OSPRH-14418

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