skip test_tagged_attachment in nova-next

This change adds
tempest.api.compute.servers.test_device_tagging.TaggedAttachmentsTest.test_tagged_attachment
to the tempest exclude regex

over the past few weeks we have noticed this test failing intermitently
and it has not started to become a gate blocker. This test is executed in other
jobs that use the PC machine type and is only failing in the nova-next
job which uses q35. As such while we work out how to address this properly
we skip it in the nova-next.

Conflicts in .zuul.yaml because 5d2f2da0af changed the same
tempest_exclude_regex and is not in xena.

Conflicts:
  .zuul.yaml

NOTE(elod.illes): conflict is due to not having the following patches
in stable/wallaby: I4f2d01a4cf443f9c539158e77032cd3d8ce24ad7 and
Ib56a034fb08e309981d0b4553b8cee8d16b10152.

Change-Id: I845ca5989a8ad84d7c04971316fd892cd29cfe1f
Related-Bug: #1959899
(cherry picked from commit b00ce99dd4)
(cherry picked from commit 70f75ac981)
This commit is contained in:
Sean Mooney
2022-02-04 12:28:10 +00:00
committed by Elod Illes
parent 57bf72bed2
commit 5b7cb876ba

View File

@@ -208,7 +208,7 @@
# (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
tempest_black_regex: ^tempest\.(scenario\.test_network|api\.compute\.servers\.test_device_tagging\.TaggedAttachmentsTest\.test_tagged_attachment)
devstack_local_conf:
post-config:
$NOVA_CPU_CONF: