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: Ia1e4677d7e09bd74d57e9b48f606ddc1febf135a
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: Ieffaedbb3bd728a27b71bc3a4f4da62ddc3bc28d
In 656104, we dropped the voting jobs because of infra issues,
this patch is to make sure we restore and make jobs voting again.
Change-Id: I935f20565e2ed382be0444eef430fa07575986a9
In [1] this package was moved to the 'devel' list mistakenly, it is
required on the compute host always.
In addition, due to infra. issues with Debian, this patch marks the
jobs as non-voting[2].
[1] https://review.opendev.org/662585
[2] https://review.opendev.org/686396
Change-Id: Iaa08e18d9da1a55a27241e4b5629eccb7969e2e0
This driver has been retired [1] and tests are now failing becasue the
nova-lxd repo master branch is now empty.
[1] https://review.opendev.org/#/c/672283/
Change-Id: I9906ede54f6b41972a03bfa1d39ba5f99c6235ed
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: Ie70a303c5b8e7a87804fa734c0ff68eaddcf9ab3
This patch adjusts the nova-lxd deployment so that it works correctly
with LXD3 and bionic.
* Update the zuul job and project config to switch from xenial to bionic.
* Change the variable lxd_storage_pool to always have a defined value
in the role defaults. This variable represents the name of the LXD
storage pool which is distinct from any names associated with underlying
storage. LXD storage pools created with 'lxd init' are always called 'default'.
* Switch the role test storage backend from dir to ZFS. nova-lxd is
currently not working for the dir backend as it expects the storage
subsystem to support quotas.
* Due to limitiations in nova-lxd it is necessary to ensure that the
LXD storage pool name and ZFS pool names are both set to 'default'.
Closes-Bug: #1800837
Change-Id: If1e48bb2e789e13f20435da19907b5adb7c1ef1f
Now that we're using the general templates, we can slim down
the role test definitions. We can also remove tests which are
not being watched, or which are fundamentally broken. With
this we can also remove unused scripts/plays.
We do the following:
1. We remove the 'ssl' job, given that the person working on
that is no longer doing so, and no-one else has picked up
the work.
2. We remove the 'upgrade' job, given that it's been broken
all cycle due to the way the job executes and we need to
regroup to figure out another way to do it.
3. We rename the tox target for 'func_lxc' to 'lxc' and
as the 'func_' prefix is pointless.
4. We remove the base python setting in the lxc tox target
because we're not running our functional tests using py3
yet.
Change-Id: Ie0e72f69026c44a3c3ff6316bbb308bdd873c149
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: Iaff845bef52268736a6808258d7d81f0f80fe64e
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: I22e03209fa51db13b55d8cc685589603252f4b35
Story: #2002586
Task: #24319
In order to have more centralized configuration, switch the role
to use the project-template instead.
Also move centos check/gate to voting as it now passes.
Change-Id: I356f122a3af8d9ddbc078265b02874936b34d4fe
Distributions provide packages for the OpenStack services so we add
support for using these instead of the pip ones.
Depends-On: https://review.openstack.org/#/c/579151/
Depends-On: https://review.openstack.org/#/c/579071/
Change-Id: Iff373b5402c664206b940b8e95a0b8845050213b
Implements: blueprint openstack-distribution-packages
Without this patch, nova upgrades are not tested.
As a reminder, Master and Queens were simulatenously broken
together due to the SPICE url change. We can now bring the
upgrades back now that the SPICE url change has been merged
in Queens [1].
The fact we do not test upgrades is a problem, as we could
miss an important upstream change, or break our upgrades
ourselves without noticing.
This patches solves the problem.
[1]: I5639ebee2d232fdac3f5fe2d38e9a54d2ff8c03a
Change-Id: I31e874ecad4525e57b85f2b09a556124a8f8829d
The extra jobs that we have are not something that is needed, we simply can
set the jobs to non-voting in the project definition and avoid having non
voting jobs.
Change-Id: Ib266cff889cbb49a5e24dac7b908033f0e8a77fa
This temporarily disable the upgrade checks, as they
will fail at getting the repo, until this gets
backported.
Change-Id: I5639ebee2d232fdac3f5fe2d38e9a54d2ff8c03a
Signed-off-by: Kevin Carter <kevin.carter@rackspace.com>
Co-Authored-By: Jean-Philippe Evrard <jean-philippe@evrard.me>
There is currently a problem with CentOS builds which
is not common to the other distributions, but the issue
is blocking patches from merging.
Until the issue is resolved, we switch the job to a
non-voting job.
Change-Id: Ic410fe6fda279955fec2472413efaa96e7de3321
Related-Bug: #1773248
The job is failing due to changes in the upstream
implementation. We set the job to non-voting for
now until the upstream fix [1] is merged.
[1] https://review.openstack.org/559190
Change-Id: Ic99e02260b6bc18a0771fea30a27b86097efe4da
There isn't a need to run non-voting jobs in gate, as it ends up just
wasting CI resources. Results can be obtained from the check pipeline
results.
Change-Id: Id17185fe699925d849a51a8e2482ef50c93aa229
Signed-off-by: Paul Belanger <pabelanger@redhat.com>
Zuul no longer requires the project-name for in-repo configuration.
Omitting it makes forking or renaming projects easier.
Change-Id: Iec95d6688b3daba0d1d0fcb4da01a31b280b1400
When 'nova_galera_use_ssl' is True, use an encrypted connection to
the database using either a self-signed or user-provided CA certificate.
A new non-voting test has been added to verify that the role remains
functional when enabling SSL features.
Change-Id: I9f9a130be3a4920170295b041b94dd435e3781d1
Partial-Bug: 1667789
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: I2df5f24a7ce2cb2aadceb395088505b99f31bd5c
This changes the a-r-r with the proper version, and fixes
the repo path for role upgrades:
The role will, during test-upgrade-pre, have its current branch
checked out, and will deploy the current branch infrastructure,
including the generation of the constraints.
Then, the installation of previous branch of the role will use
the constraints for its previous version, but will have no
constraints for it, and fail.
We need to generate the constraints for the previous version too.
This should do it.
This patch also 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.
Co-Authored-By: Jean-Philippe Evrard <jean-philippe.evrard@rackspace.co.uk>
Depends-On: I0391ec310c4eede436011a48490e3c524c8ddf4d
Change-Id: Ib35253ed9020ed27280329891509292b5b463d6c
Dmitriy Rabotyagov