yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #64508
[Bug 1689238] Re: Do not disable qos scenario unconditionally
Reviewed: https://review.openstack.org/463268
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=8528ea2b0e45379ce29ba6e1cfe17c5ae4197592
Submitter: Jenkins
Branch: master
commit 8528ea2b0e45379ce29ba6e1cfe17c5ae4197592
Author: YAMAMOTO Takashi <yamamoto@xxxxxxxxxxxx>
Date: Mon May 8 16:49:06 2017 +0900
Disable QoS scenario tests differently
The test was disabled due to some issues in the reference implementation.
CIs for other implementations might not want to disable it.
Closes-Bug: #1689238
Related-Bug: #1662109
Change-Id: I36357e2ef967db3a73c2341903cd18f5109a006b
** 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/1689238
Title:
Do not disable qos scenario unconditionally
Status in neutron:
Fix Released
Bug description:
qos scenario test is disabled in neutron for bug 1662109.
the bug doesn't seem related to midonet implementation.
note that the tempest plugin is used by subprojects' gate jobs.
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1689238/+subscriptions