yahoo-eng-team team mailing list archive

[OpenStack Infra <1694396@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://review.openstack.org/468982
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=55d810c7e68dd5379a55da45f1cf43ac78573497
Submitter: Jenkins
Branch:    master

commit 55d810c7e68dd5379a55da45f1cf43ac78573497
Author: YAMAMOTO Takashi <yamamoto@xxxxxxxxxxxx>
Date:   Tue May 30 03:01:26 2017 +0000

    Revert "Change list of available qos rules"
    
    This reverts commit 3299cdffae5cd7196a1676da103da5e2e413ec21.
    
    At least, there's a user which relies on the previous
    semantics. (Our tempest plugin)
    We should not change API semantics lightly
    in an incompatible way.
    
    Closes-Bug: #1694396
    Related-Bug: #1694190
    Change-Id: I88a216951d8996ac8bc90078b4239f0d25392e58


** Changed in: neutron
       Status: In Progress => Fix Released

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

Title:
   qos scenario tests should be skipped if rule type is not supported

Status in neutron:
  Fix Released

Bug description:
  related bug 1694190

  it should skip if the functionality is not supported.
  it has require_qos_rule_type check but it's broken after the recent api semantics change. [1]
  the problem is that if a deployment has multiple drivers and one of them doesn't support the
  rule type, the test doesn't skip (anymore) and can fail.

  [1] Ia00d349625db358ab486802fc0ff2e69eaa3895e

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