From 15c59f1897771e696cbce167379b9ac968c255db Mon Sep 17 00:00:00 2001 From: Matt Riedemann Date: Thu, 5 Dec 2019 09:55:28 -0500 Subject: [PATCH] Skip test_minbw_allocation_placement in nova-next job We just recently enable this scenario test [1] but it's causing the nova-next job to intermittently fail because the nova-next job runs the tempest compute API and scenario tests concurrently (unlike the tempest-full job which runs the API tests concurrently and then the scenario tests serially) and the scenario test is creating a public shared network which causes the compute API tests, when creating a server without specifying a network, to fail since nova doesn't know which network to use. So for now just blacklist the scenario test until the related tempest bug is fixed. [1] https://review.opendev.org/#/c/697180/ Change-Id: Ie0e6136e88bedb2c4c6d0b742319627d58da147e Related-Bug: #1844568 --- .zuul.yaml | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/.zuul.yaml b/.zuul.yaml index 30893abd4770..ae5116eb5cb1 100644 --- a/.zuul.yaml +++ b/.zuul.yaml @@ -176,7 +176,9 @@ # (1) take a long time and (2) are already covered in the # tempest-slow* job. If this regex gets more complicated use # tempest_test_blacklist. - tempest_black_regex: ^tempest.scenario.test_network + # TODO(mriedem): Unskip test_minbw_allocation_placement once bug 1844568 + # is fixed. + tempest_black_regex: ^tempest.scenario\.(test_network|test_minbw_allocation_placement) devstack_local_conf: post-config: $NOVA_CPU_CONF: