QoS policy with minimum bandwidth rules can be assigned to a VXLAN network if the network doesn't have any ports

Bug #1913180 reported by Rodolfo Alonso
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
neutron
Fix Released
Low
Mamatisa Nurmatov

Bug Description

Description of problem:
Minimum bandwidth QoS rule is only applicable for the network which is backed by physical networks,
thus it should be rejected for vxlan networks, which is not associated with specific physical networks.

This is enforced in api level when a network has any port, but is NOT enforced properly if a network has no ports.

How reproducible:
Always

Steps to Reproduce:
1. Deploy overcloud with ml2+ovs
2. Create a QoS policy and add minimum baidwidth QoS rules to it
3. Create a vxlan network
4. Set the qos policy (2) on the netwokr (3)

Actual results:
Updating network policy is not rejected

Expected results:
Updating network policy is rejected

Bugzilla reference: https://bugzilla.redhat.com/show_bug.cgi?id=1917648

Tags: qos
Changed in neutron:
importance: Undecided → Low
tags: added: qos
Revision history for this message
Mamatisa Nurmatov (isabek) wrote :

Rodolfo, can I take this bug for fixing or you will do it by yourself?

Changed in neutron:
assignee: nobody → Mamatisa Nurmatov (isabek)
Revision history for this message
Rodolfo Alonso (rodolfo-alonso-hernandez) wrote :

Hello Mamatisa:

You are more than welcome to help fixing this bug.

Thanks a lot.

Changed in neutron:
status: New → Fix Committed
Changed in neutron:
status: Fix Committed → In Progress
Changed in neutron:
status: In Progress → Fix Committed
Revision history for this message
Rodolfo Alonso (rodolfo-alonso-hernandez) wrote :
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/neutron 16.3.1

This issue was fixed in the openstack/neutron 16.3.1 release.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/neutron 17.1.1

This issue was fixed in the openstack/neutron 17.1.1 release.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/neutron 18.0.0.0rc1

This issue was fixed in the openstack/neutron 18.0.0.0rc1 release candidate.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to neutron (stable/train)

Fix proposed to branch: stable/train
Review: https://review.opendev.org/c/openstack/neutron/+/787377

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on neutron (stable/train)

Change abandoned by "Mamatisa Nurmatov <email address hidden>" on branch: stable/train
Review: https://review.opendev.org/c/openstack/neutron/+/787377
Reason: Dependency patch was abandoned https://review.opendev.org/c/openstack/neutron/+/787492

Revision history for this message
Rodolfo Alonso (rodolfo-alonso-hernandez) wrote :
Changed in neutron:
status: Fix Committed → Fix Released
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.