yahoo-eng-team team mailing list archive

[Slawek Kaplonski <1779054@xxxxxxxxxxxxxxxxxx>]

I think that this issue is related more to how OpenStack client handles such errors returned from API and You should open it against OSC in storyboard.
Neutron is reporting correctly that this rule type is not supported by this backend.

** Changed in: neutron
       Status: New => Invalid

** Tags added: qos

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

Title:
  QoS – cannot associate policy with “minimum bandwidth” rule to port

Status in neutron:
  Invalid

Bug description:
  ### Scenario: ###
  1) Create a new QoS policy with:
  openstack network qos policy create bandwidth-control

  2) Create a new rule of “minimum bandwith” type and associate this rule to previously created policy with:
  openstasck network qos rule create --type minimum-bandwidth --min-kbps 10000 --egress bandwidth-control

  3) Set VM port to use QoS policy with:
  openstack port set --qos-policy bandwidth-control vm1_port

  ### Actual Result: ###
  Getting “Unknown error” in CLI, in spite of the fact that reason for this failure is known, at least in neutron’s server.log (Rest API messages) and it’s logged with: “Rule type minimum_bandwidth is not supported by openvswitch”
  See attached server.log file

  ### Expected Result: ###
  CLI output should contain the same info as API, so Instead of “unknown error” we should prompt “Rule type minimum_bandwidth is not supported by openvswitch”

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