Run script generate-gitmodules.py to sync with governace repository to
add new repositories and remove retired ones.
Change-Id: Ia42b717ad242958ba4a9689ac814c956f460712f
* Update congress-tempest-plugin from branch 'master'
- add check jobs for stable/stein and stable/train
Change-Id: I650abab94a9510e827b2d803170c979b656ccf05
* Update congress-tempest-plugin from branch 'master'
- Bump the openstackdocstheme extension to 1.20
Some options are now automatically configured by the version 1.20:
- project
- html_last_updated_fmt
- latex_engine
- latex_elements
- version
- release.
Change-Id: Ifab1917e7a2743a5c309a1ef3729c87f1a49e727
* Update congress-tempest-plugin from branch 'master'
- Add Python 3 Train unit tests
This is a mechanically generated patch to ensure unit testing is in place
for all of the Tested Runtimes for Train.
See the Train python3-updates goal document for details:
https://governance.openstack.org/tc/goals/train/python3-updates.html
Change-Id: I894fb344e442a83e7478b51a82fd65e53900e8df
* Update congress-tempest-plugin from branch 'master'
- publish congress tempest plugin doc
Current documentation link return 404
- https://docs.openstack.org/congress-tempest-plugin/latest
Adding the doc publish job to publish the documents on above site
Change-Id: If2cbaf39f49effad5c3b82363604504306c9d2ce
* Update congress-tempest-plugin from branch 'master'
- Update api-ref location
The api documentation is now published on docs.openstack.org instead
of developer.openstack.org. Update all links that are changed to the
new location.
Note that redirects will be set up as well but let's point now to the
new location.
For details, see:
http://lists.openstack.org/pipermail/openstack-discuss/2019-July/007828.html
Change-Id: I171eb7efc0e34b4451a1b3539ae6655f81dd2312
* Update congress-tempest-plugin from branch 'master'
- Changes for url transition to OpenDev
This commit changes openstack.org URL to opendev.org URL
Change-Id: I4f67a9afffa12b07da554f6f3c696276d57f5de6
- OpenDev Migration Patch
This commit was bulk generated and pushed by the OpenDev sysadmins
as a part of the Git hosting and code review systems migration
detailed in these mailing list posts:
http://lists.openstack.org/pipermail/openstack-discuss/2019-March/003603.htmlhttp://lists.openstack.org/pipermail/openstack-discuss/2019-April/004920.html
Attempts have been made to correct repository namespaces and
hostnames based on simple pattern matching, but it's possible some
were updated incorrectly or missed entirely. Please reach out to us
via the contact information listed at https://opendev.org/ with any
questions you may have.
* Update congress-tempest-plugin from branch 'master'
- Replace openstack.org git:// URLs with https://
This is a mechanically generated change to replace openstack.org
git:// URLs with https:// equivalents.
This is in aid of a planned future move of the git hosting
infrastructure to a self-hosted instance of gitea (https://gitea.io),
which does not support the git wire protocol at this stage.
This update should result in no functional change.
For more information see the thread at
http://lists.openstack.org/pipermail/openstack-discuss/2019-March/003825.html
Change-Id: I8833914dcfd75441bf99074d33802c5b26852928
* Update congress-tempest-plugin from branch 'master'
- Merge "Add python 3.6 to setup.cfg, in line with Stein target"
- Add python 3.6 to setup.cfg, in line with Stein target
Change-Id: I6bc89de9c4a29e50fd98f0dfbaa47abe1c32ee2f
* Update congress-tempest-plugin from branch 'master'
- Move legacy job to bionic and stable on xenial
We are migrating all the legacy jobs to bionic now
- https://review.openstack.org/#/c/639096
Above patch move all the legacy base jobs to bionic which
will automatically move all derived jobs to bionic.
As congress-tempest-plugin is branchless so these jobs running
on stable branch needs to be on xenial and this also has been
taken care in base patch.
stable job running on master gate has to be on xenial.
This commit keep the stable branch master job on xenial
and rest all on bionic.
Depends-On: https://review.openstack.org/#/c/639096
Change-Id: Id4e0312ff5093aae9704e400bfa74803520bc0e4
* Update congress-tempest-plugin from branch 'master'
- Update nova server test for addiing created_at field
Change-Id: I5f91eb68faa9dc355b096de341afad27cb0f710b
* Update congress-tempest-plugin from branch 'master'
- Add test for servers.addresses table in nova driver
This commit will test for changes in congress nova driver
that adds addresses table.
Change-Id: Ib948d7be1dc28a49f36488eb0860d0839cbdee60
Partially-Implements: blueprint add-tacker-datasource-driver
* Update congress-tempest-plugin from branch 'master'
- Resolve test_datasource_db_sync_add_remove instability
Configure the replica server in the test to use a short PRC timeout.
The instability appears to arise as follows.
In starting the replica Congress instance:
If Congress API process starts before Congress policy engine process,
the call to check Congress started is processed by the API process,
which makes an RPC call to the policy engine process.
But the policy engine process may be a bit slower to start.
In that case, the RPC call may never reach the policy engine process
even if the policy engine process starts up just a few seconds later.
So the call times out according to the default 60 seconds, by which
point the entire retry period of the test is used up and the test
fails.
In this fix, the RPC timeout is set to a short 10 seconds on the
replica instance. That way, if the policy engine has not started
by the time of the first RPC call, the RPC call would time out with
time remaining on the test retry period for further retry.
The test retry period is also increased because occassionally the
replica policy engine takes longer than the allotted 60s to start up.
Change-Id: Ied8c95c4a60a3b6ea2c617fdfe94d4d7cf7a5822
* Update congress-tempest-plugin from branch 'master'
- 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
* Update congress-tempest-plugin from branch 'master'
- Merge "Neutron driver test use admin"
- Neutron driver test use admin
In current test setup, congress neutron driver uses admin credential
but the corresponding tempest test uses non-admin credential. As a
result, the driver and the test verifying the driver's data sometimes
see different data, causing false test failure.
This patch makes the test use admin credentials.
Change-Id: I6116e8027f5dfcceb6dd835de055cc3f8040d45c
* Update congress-tempest-plugin from branch 'master'
- Add policy eval tests to vitrage webhook driver
To properly test for the publishing aspect of the driver.
Depends-On: https://review.openstack.org/#/c/625749/
Depends-On: https://review.openstack.org/#/c/629029/
Change-Id: I3cb1b1c3e80b49ddbaa9f53506d12abf4f697174
* Update congress-tempest-plugin from branch 'master'
- Merge "Update CI jobs in sync with migration in congress repo"
- Update CI jobs in sync with migration in congress repo
- Run newly migrated congress-tempest-* jobs from congress repo.
- Hold legacy jobs and playbooks deleted from congress repo. They
are used to run jobs against stable branches. Can be removed when
all supported stable branches use new style jobs.
- Fixes the problem where stable branch jobs do not correctly use
the specified branches.
Depends-On: https://review.openstack.org/#/c/631609/
Change-Id: I03cfb7a1dae0ee3fab70be61203fc07f324e8a41
* Update congress-tempest-plugin from branch 'master'
- Merge "Modify monasca-webhook test"
- Modify monasca-webhook test
This commit adds test for modified monasca webhook driver[0]
That will test for 3 different tables names alarm-notification,
metrics and dimensions.
[0] https://review.openstack.org/#/c/596698/
Depends-on: If6138710a0ee29320c3bdbefaffb9cc5df4b90c0
Depends-on: I1412840373fd8fe4e153e60d5ef85241c1a6e817
Change-Id: I77241a735e0f16a4617b9eb9fbd73afe426ed2f8
Partially-Implements: blueprint add-monasca-push-driver
* Update congress-tempest-plugin from branch 'master'
- Merge "Monasca webhook rocky schema feature flag"
- Monasca webhook rocky schema feature flag
Monasca webhook driver was released in rocky as 'unstable'.
As expected, backward incompatible changes are taking place.
To support tempest testing of the feature in Rocky, an additional
feature flag is needed to indicate the old Rocky schema is used.
Change-Id: Ie605a5d8427af6191a76dcf6ebfbc3e69e141248
* Update congress-tempest-plugin from branch 'master'
- Merge "Fix queens py35 job"
- Fix queens py35 job
Current job of queens py35 try to override
the stable/queens branch using override_branch
var which is zuulv3 var not legacy zuul job.
On legacy zuul job, branch can be overridden by
BRANCH_OVERRIDE var.
This is problem in all stable branch job running
on congress-tempest-plugin master gate. Other stable
branch job somehow not failing and master version of all
repo are working fine there but they do not actually test
stable branch.
queens py35 job is failing when using master version
of other repo.
Plan is to migrate thw congress jobs to zuulv3 which
will be easy to fix and use override_branch for all
stable branch jobs running on master. But this can
take time so let's fix broken job only as of now.
This commit fixes this job only to unblock the gate.
Change-Id: I328cf0330a054e76e8ac7895a2f844fdb7ab4226
* Update congress-tempest-plugin from branch 'master'
- add z3 support_builtins feature flag
To properly skip the tests for older versions of Congress.
Minor spelling errors also corrected.
Change-Id: Ib848e1a79daab8dc9b5081b4ace975bd060d1372