Fraction RX_TX value not getting applied to Neutron Queue QOS

Bug #1463085 reported by Raghu Katti
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
neutron
New
Undecided
Unassigned

Bug Description

I noticed this in Icehouse using Neutron backed by NSX.

Not sure if it is related to a similar issue that was fixed : https://review.openstack.org/#/c/188560/1

Following are steps to reproduce it :

1. Create flavor with RX_TX as 0.25 and 1.5

2. Create a neutron qos queue with max bandwidth value of 1024

3. Create a network with queue_id attached

4. Spin a VM with flavor having RX_TX value of 0.25

5. Execute neturon queue-list.

+--------------------------------------+--------------+-----+------+-------------+------+---------+
| id | name | min | max | qos_marking | dscp | default |
+--------------------------------------+--------------+-----+------+-------------+------+---------+
| 1b67eeb5-8568-43da-a7de-4bf4248b874d | qostestqueue | 0 | 1024 | untrusted | 0 | False |
| efe223ab-c8aa-46bc-bc62-504dba6f7960 | qostestqueue | 0 | 1024 | untrusted | 0 | False |
+--------------------------------------+--------------+-----+------+-------------+------+---------+

Expected max value was 256 instead we see 1024. Similar issue is seen creating flavor with RX_TX of 1.5

It works for non fractional RX_TX values e.x. for RX_TX we do see a neutron queue with max value of 5120

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.