qos rules are not applied to trunk subports
Bug #1624570 reported by
Armando Migliaccio
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Fix Released
|
Medium
|
Armando Migliaccio |
Bug Description
Change [1], introduced a device_owner for trunk sub-ports. However, it was overlooked that device_owner is used by QoS to determine whether to process the port and apply QoS rules [2,3,4].
Right now there is not active coverage that ensures that QoS and Trunk are indeed compatible but as we stand right now, they clearly cannot as the code forbids applying rules to anything whose device_owner starts with 'network:' or 'neutron:'.
We need to figure out a way to solve the conundrum.
[1] https:/
[2] https:/
Changed in neutron: | |
milestone: | none → newton-rc2 |
tags: | removed: newton-rc-potential |
To post a comment you must log in.
Mitigation action right now would be to clear the device_owner with neutron port-update, but a more long term solution must be found.