yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #80877
[Bug 1854993] Re: QoS bandwidth tempest test no longer running
Reviewed: https://review.opendev.org/697180
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=f347839151a78f9fbc70c79f017fb0e96438465c
Submitter: Zuul
Branch: master
commit f347839151a78f9fbc70c79f017fb0e96438465c
Author: Eric Fried <openstack@xxxxxxxx>
Date: Tue Dec 3 14:09:38 2019 -0600
Add QoS tempest config so bw tests run
In [1] the tempest-slow-py3 job was dropped and non-redundant bits
folded into the nova-next job.
Except we forgot to move over some of the config necessary to make this
QoS bandwidth test [2] work, so it gets skipped:
setUpClass (tempest.scenario.test_minbw_allocation_placement.MinBwAllocationPlacementTest)
... SKIPPED: Skipped as no physnet is available in config for placement based QoS allocation.
This syncs the nova-next job with the config like what was done for
tempest-slow here [3]. Some of that was already in place (to make
QoS heal allocation testing work).
[1] https://review.opendev.org/#/c/683988/
[2] https://github.com/openstack/tempest/blob/3eb3c29e979fd3f13c205d62119748952d63054a/tempest/scenario/test_minbw_allocation_placement.py#L142
[3] https://github.com/openstack/tempest/commit/c87a06b3c29427dc8f2513047c804e0410b4b99c
Closes-Bug: #1854993
Change-Id: Ib9332b8677c4ccb9e38b6fcdf39e989a891a56fe
** Changed in: nova
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1854993
Title:
QoS bandwidth tempest test no longer running
Status in OpenStack Compute (nova):
Fix Released
Bug description:
In [1] the tempest-slow-py3 job was dropped and non-redundant bits
folded into the nova-next job.
Except we forgot to move over some of the config necessary to make
this QoS bandwidth test [2] work, so it gets skipped:
setUpClass
(tempest.scenario.test_minbw_allocation_placement.MinBwAllocationPlacementTest)
... SKIPPED: Skipped as no physnet is available in config for
placement based QoS allocation.
We think we just need to get the nova-next job synced up with the
config like what was done for tempest-slow here [3].
[1] https://review.opendev.org/#/c/683988/
[2] https://github.com/openstack/tempest/blob/3eb3c29e979fd3f13c205d62119748952d63054a/tempest/scenario/test_minbw_allocation_placement.py#L142
[3] https://github.com/openstack/tempest/commit/c87a06b3c29427dc8f2513047c804e0410b4b99c
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1854993/+subscriptions
References