-
Bug
-
Resolution: Done-Errata
-
Normal
-
rhos-18.0.z
-
None
-
3
-
False
-
-
False
-
?
-
openstack-neutron-22.2.2-18.0.20250307064740.51e19bb.el9osttrunk
-
None
-
-
-
Neutron Sprint 9, Neutron Sprint 10, Neutron Sprint 11
-
3
-
Moderate
In [1], the Neutron API checks the validity of the QoS rules before adding them to a policy:
- If a new max-bw rule is lower (max-kbps) than a min-bw rule, the check will fail.
- Same for a min-bw rule, if the min-kbps value is greater than the max-bw rule, the check will fail.
The problem here is that this check doesn't match the rule direction. This can be tested using the following reproducer:
$ openstack network qos policy create qos_test
$ openstack network qos rule create --type bandwidth-limit --max-kbps 2000 --egress qos_test
$ openstack network qos rule create --type minimum-bandwidth --min-kbps 1500 --egress qos_test
$ openstack network qos rule create --type minimum-bandwidth --min-kbps 3000 --ingress qos_test
The latest command will fail despite that the min-bw rule with value 3000 has "ingress" direction and the max-bw rule with value 2000 has "egress" direction.
- links to
-
RHBA-2025:147941 Release of components for RHOSO 18.0
- mentioned on