This role was shared with tripleo, but that project is now
deprecated so there is no need to carry the cross-project CI jobs
any more.
Change-Id: I73aec0f325708f42bbd0fd07d572fb833e8dfb2c
'--whitelist-file' option is deprecated, use '--include-list' instead which is functionally equivalent.
Right now Tempest still supports this option for backward compatibility, however, it will be removed soon.
This change addresses the occurences of whitelist and blacklist in the os_tempest OSA role.
Change-Id: Id021d084867ef2891c381c5863b82421e90ee2ca
We've created integrated linters check job a while back and it's successfully
working for several releases. At the moment we experience difficulties
with future maintenance of the linters check from the openstack-ansible-tests
repo. So instead of fixing current one, we replace it with modern version of
the test.
Change-Id: I34789f52da45bb169d76b822208c05e53d8984de
Since we copy all release notes to the integrated repo there is not need
in publishing release notes for each repository. We should only verify their
validity and linting.
Change-Id: Ifeb20f22c226ec36abbb81fd93ffe6ad3ad9fc89
This change migrate c8 jobs/templates to content provider
jos so consumer jobs can use resources built by provider
jobs.
Change-Id: I45894a47b9a43c47abade2018d7afd43b2392b4f
Signed-off-by: Amol Kahat <amolkahat@gmail.com>
Some periodic jobs on tripleo that still run centos-7 jobs for other
branches require this variable.
This file was removed by 5a46aff857
Also adding a centos-7 standalone job for coverage.
Change-Id: I85b2841591990fc91ec665b8f77e4ceb50766c6c
Closes-Bug: #1900443
The tempest init was checking if the workspace/etc directory exists, and
were creating a new workspace without pass a name, the default is
workspace, but passing a --name ensure it won't break if tempest decides
to change it.
Also, the rename command only change the name in the
$HOME/.tempest/workspace.yml, it doesn't change the path for the
particular workspace. The same happens with the move command, it just
update the path on the workspace.yml file.
With this patch, the tempest workspace is being moved properly to a
workspace_$CURDATE, all the files are copied to the new workspace,
delete the old workspace directory, and call tempest init properly.
Also adding tripleo upgrade job as nv for now, since this issue only
happen in upgrade jobs.
Change-Id: I8a3b79352819f5e980eaea7482cd6b1f1bfc47be
Closes-Bug: #1896126
Do some role cleanup to path for not supported OS,
like gentoo or suse.
This includes bionic distro jobs, since this path is not supported
for bionic in Victoria
Fix ansible linter errors as a result of linter update.
Change-Id: I619dc6da251bd9d6f9d117e7b0cdedc2e59bf581
Previously the tempest plugins were installed using pip independant
of the python_venv_build role, in the past OSA could support a mixed install
of a distro tempest package and source code plugins. The mixed mode has been
removed but the tempest & tempest plugins installation tasks remain seperate.
Tempest is installed using python_venv_build, and the plugins are installed
directly using the ansible pip module. Unfortunatly, these two approaches do
not handle openstack upper-constraints in the same way, particularly for a
package that is installed from source code.
The python_venv_build role will correctly install a version of tempest
corresponding to the specified git SHA even when u-c specifies an earlier version
of the package. Unfortunately, when installing the tempest plugins with
the pip module, the previously installed tempest packages gets downgraded to
match the version specified in u-c as the pip module is unaware of the combined
source + u-c constraints generated by python_venv_build.
Tempest is an unusual case, because it is perhaps the only "top level" openstack
projects which has its own constraint appear in u-c.
This patch also corrects the use use of the venv_wheel_build_enable variable.
As a role default the value of this variable is changed in the whole scope of
the role becasue it is overridden during the stackviz install. The approach
used should be reviewed and refined in a future patch.
This patch also marks bionic/distro jobs as non voting as there has not been
a release of tempest which passes keystone test_list_user_groups test.
Change-Id: I5e8c8540b30865aaccafe59c73fae6fdd6da80a8
This sets the molecule framework files and job, so later we can write
tests for the role using it.
Change-Id: I16a67ff8acbadc7dce3746ca2ffc67aed660ed65
tripleo-ci-centos-7-standalone-os-tempest was added while porting
tripleo ci jobs to os_tempest and now the porting is done.
tripleo-ci-centos-7-standalone-os-tempest and
tripleo-ci-centos-7-standalone are the same job, It replaces the
existing os_tempest job to plain tripleo standalone job to keep
consistency at all places.
Change-Id: I4e9d5b93be36c9c0cf1b0f6eaec3951130635cd8
Signed-off-by: Chandan Kumar (raukadah) <chkumar@redhat.com>
Due to the shift from git.openstack.org to opendev.org none of
the depends-on features are working. The patches to fix that
cannot merge until https://review.opendev.org/657778 merges.
In order to enable this to merge, we temporarily disable voting
for this failing job. Once the above match merges, we can revert
this patch.
Depends-On: https://review.opendev.org/657816
Change-Id: I75f116fc226fc1821ab88835c89b2e64a28c7dbf
In order to do a more complete verification of any patches,
we add a full uncontainerised OpenStack deployment to the
functional testing using the integrated repo. This replaces
the previous role functional test mechanism.
Any additional role tests are left as-is. They will require
some extra implementation in the integrated build before they
can be transferred.
Depends-On: https://review.openstack.org/647840
Depends-On: https://review.openstack.org/648502
Depends-On: https://review.openstack.org/648551
Change-Id: Idab108649076b24d526e9dd7d6569f306e220df2
Since https://review.openstack.org/#/c/627500 marks the integration
of os_tempest in tripleo ci, it is good to have a job here to make
sure that it does not break tripleo integration.
Change-Id: Ib6f2589b45a2273b124d78567d1da7c4cf605997
Since os_tempest already have support to python-tempestconf, adding a
job that test it on check and gate.
Change-Id: I2ae6057d197a7f7f40b2bb544dc2381ab8044aed
In order to consume os_tempest role across different deployment
tools, following changes are introduced:
- tempest_install_method:distro|source through which user can install
tempest from source as well as distro
- tempest_workspace directory is added as when tempest is installed
from distro, we need a place where tempest can be executed. It
generalised the use of tempest_workspace at each place.
- The default location of the default tempest configuration is now
/etc/tempest/tempest.conf rather than the previous default of
$HOME/.tempest/etc.
Change-Id: Ie280cfa6b93fa65c56ed98066deb4f9c82a1a8db
This is a mechanically generated patch to switch the documentation
jobs to use the new PTI versions of the jobs as part of the
python3-first goal.
See the python3-first goal document for details:
https://governance.openstack.org/tc/goals/stein/python3-first.html
Change-Id: Icfd7d32b9b71c498ce206ba1f28b0e32e9fbfd97
Story: #2002586
Task: #24319
This is a mechanically generated patch to complete step 1 of moving
the zuul job settings out of project-config and into each project
repository.
Because there will be a separate patch on each branch, the branch
specifiers for branch-specific jobs have been removed.
Because this patch is generated by a script, there may be some
cosmetic changes to the layout of the YAML file(s) as the contents are
normalized.
See the python3-first goal document for details:
https://governance.openstack.org/tc/goals/stein/python3-first.html
Change-Id: I282dcef2584edb8aedeac93943b6ee8b1946f4c9
Story: #2002586
Task: #24319
In order to have more centralized configuration, switch the role
to use the project-template instead.
Depends-On: I3df2c670beeb78baaa1515bcd27e8f2b0d95b3a9
Change-Id: I995d4da20d592e519d990c38f47a5243e9575846
Zuul no longer requires the project-name for in-repo configuration.
Omitting it makes forking or renaming projects easier.
Change-Id: I0d6269d93a8fe409740a8f3095121b1a914ffd3c
Initially the intent for adding this was to better test
any patches for roles together before they merge, but it
has had the unintended side-effect of causing patches to
take much longer to merge (because they all get lined up
in a single queue, rather than independent queues) and
a lot more infra resources are used (because a patch
that fails at the top of the queue will result in all
subsequent patches restarting all their tests).
As discussed in the channel, we'd prefer to revert back
to the previous independent queue method of testing. It
has served us well.
Change-Id: Ie5f973b243e6914f4927fd9ca3afc60d45e2af18
This patch implements an initial set of jobs intended to match
the current job execution method. It does not intend to improve
how the jobs are executed - only to replicate what is currently
in openstack-infra/openstack-zuul-jobs and provide the platform
to iterate on.
Depends-On: I0391ec310c4eede436011a48490e3c524c8ddf4d
Change-Id: I695084aa70d6bd48cd8d498556918a1fbbc3c2a2
Jonathan Rosser