yahoo-eng-team team mailing list archive

[Rodolfo Alonso <1913180@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

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

** Affects: neutron
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1913180

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

Status in neutron:
  New

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

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