congress-tempest-plugin/playbooks/legacy
Eric K 2b4c0ba868 disable murano scenario test in queens-py35 job
Persistent instability in the test on queens branch and only in the
py35 job (py27 seems fine).
The instability makes the test more trouble than it's worth.
Because we are unlikely to make changes to queens going forward,
and even less likely that the changes would break murano integration,
it makes sense to simply disable to test for queens-py35 job, but
keeping it in all other jobs including queens-py27.

Also folding in the following patch resolving gate instability because
both patches are blocked on its own.
---------------------------------------
Increase policy rule create retry limit

Because in the vitrage pub-sub tests, occassionally the retry runs
out before the schema from the datasource is available to the
policy engine to allow the creation of the test rule.

https://review.openstack.org/#/c/637681/

Change-Id: I4915023258b455005e1ac2e2d1492beb368f0184
2019-02-19 21:09:10 +00:00
..
congress-devstack-api-base Update CI jobs in sync with migration in congress repo 2019-01-17 17:11:06 -08:00
congress-devstack-api-py27-queens Update CI jobs in sync with migration in congress repo 2019-01-17 17:11:06 -08:00
congress-devstack-api-py27-rocky Update CI jobs in sync with migration in congress repo 2019-01-17 17:11:06 -08:00
congress-devstack-api-py35-queens disable murano scenario test in queens-py35 job 2019-02-19 21:09:10 +00:00
congress-devstack-api-py35-rocky Update CI jobs in sync with migration in congress repo 2019-01-17 17:11:06 -08:00
congress-devstack-py35-api-mysql Update CI jobs in sync with migration in congress repo 2019-01-17 17:11:06 -08:00
congress-pe-replicated-base Update CI jobs in sync with migration in congress repo 2019-01-17 17:11:06 -08:00