Make nova-multi-cell job voting and gating
Compared to tempest-full-py3 and tempest-slow-py3 the nova-multi-cell job has been relatively stable for the past couple of months so let's make it voting so we don't regress multi-cell functionality. Change-Id: I11081177abfe2fb69fbd8fc17464c9f08962ab4c
This commit is contained in:
+1
-3
@@ -291,9 +291,6 @@
|
||||
cells. The compute on the controller runs in cell1 and the compute
|
||||
on the subnode runs in cell2.
|
||||
irrelevant-files: *dsvm-irrelevant-files
|
||||
# TODO(mriedem): Make this job voting and gating once we're happy with
|
||||
# its relative stability.
|
||||
voting: false
|
||||
vars:
|
||||
# We use the "all" environment for tempest_test_regex and
|
||||
# tempest_test_blacklist.
|
||||
@@ -391,6 +388,7 @@
|
||||
- nova-live-migration
|
||||
- nova-tox-functional
|
||||
- nova-tox-functional-py36
|
||||
- nova-multi-cell
|
||||
- nova-next
|
||||
- tempest-integrated-compute:
|
||||
irrelevant-files: *dsvm-irrelevant-files
|
||||
|
||||
Reference in New Issue
Block a user