This is an automatically generated patch to ensure unit testing
is in place for all the of the tested runtimes for antelope. Also,
updating the template name to generic one.
See also the PTI in governance [1].
[1]: https://governance.openstack.org/tc/reference/project-testing-interface.html
Change-Id: I0d94b9941a9ab5ee1b03f6ddce84b9c584421d03
As of Zed jsonschema version has been bumped to 4.14.0 in
upper-constraints, which means project should support running with
this version. This patch aims to fix ApiValidator that is not compatible
with new jsonschema.
Other deprecations, like FormatChecker.cls_checks decorator are left
intact and must be covered with follow-up patches.
We also move zuul queues to project scope as otherwise jobs do not
run due to config error.
We also replace iteritems with six method as iteritems have been dropped
from Python 3.
Change-Id: Ia8b69587aa9b3d04ffcdea7c6b97a8ae65f67534
In Zed, we have dropped the python 3.6/3.7[1] testing
and its support. Removing the py36 centos8 job as well as
updating the python classifier also to reflect the same.
[1] https://governance.openstack.org/tc/reference/runtimes/zed.html
Change-Id: I96076a685482d01ed095803ff716de06afd01816
Since Flask 2.1, the same blueprint cannot be registered multiple
times with different url_prefix values, unless the 'name' parameter
is set. Otherwise the following error is reported: "The same blueprint
cannot be registered with the same name. Use name= when registering
to specify a unique name."
At the same time, disable the openstack-ansible job,
which started to fail again, but at this point the priority
is to unblock the gates.
Change-Id: I50df2fec3fd312082a14ef2a5b6774a2515afb44
This should allow testing of un-merged changes to sahara in the
context of an openstack-ansible deployment
Story: 2009081
Task: 42894
Depends-On: I1bde4186335cb6638d2c90f5eeee1cf7944e1415
Depends-On: I123d32a0967d5196723f57a40ab5acfa7a53a440
Change-Id: Ib6e09ab83b277704a603c02f0927054478cef8a7
The tenant argument of RequestContext is no longer available since
oslo.context >= 4.0.0 . This change fixes the compatibility issue
caused by that removal.
NOTE:
Because scenario jobs are still broken with this change, these jobs
are made non-voting temporally to unblock the other jobs. Currently
this issue is blocking package build in RDO.
Story: 2009921
Task: 44779
Change-Id: I1bc81b3c13d2c08bc175d0d4f4365de7b4f71cf9
... because it was already removed from cinder[1].
Note:
The sahara-openstack-ansible-functional job is made non-voting now
because it doesn't pull code changes. This issue is reported in [2]
and will be addressed separately.
[1] e05b261af7dcd24096b229860df65dff1d385910
[2] https://storyboard.openstack.org/#!/story/2009081
Change-Id: I10261693216ca93faa49d22f2827a939114d234d
The devstack tail_log function has been deprecated since before Queens
and it has only printed a warning since then. It has been finally
removed from devstack in I7bd440adf2ce8283e3ad3d5d09e6b2b877e2b42e.
The sahara-grenade job is failing and it will continue to fail until
the heat devstack plugin is fixed on all stable branches
(currently broken due to the usage of an older Fedora image which
doesn't exist anymore, see Id869f83a46454897c2fe7a532eebfa2863befe5e),
so disable it.
Change-Id: I921d7bac5963c66e14a6a06b100d624924914f5a
The tripleo jobs decided unilaterally, and without even trying
to discuss it, to remove sahara from scenario003.
Baffling to say the least.
Change-Id: I03e297296e9dcf197f12bc1516f7e1b93ef367b7
Based on the native 'grenade' job.
Also, remove the now-unneeded scenario-py3 job
(probably a leftover).
Story: 2001686
Task: 24518
Depends-On: https://review.opendev.org/548936
Change-Id: I7efddc3c9bbf3ea9c635d6cbe5835e46de017ec3
- TriploO: inherit from the standalone job based on scenario003,
which is the one where Sahara is deployed;
- OSA: inherit from openstack-ansible-cross-repo-functional, which
is apparently meant to be used for this.
Change-Id: I823bfed2f0b69e66ec28098f5df98a63f3e73e55
Requirements:
- bandit 1.6.0 contains a regression in the handling of patterns.
A fix is in place in bandit master, but newer versions introduces
more checks so they are not working as well.
The version is excluded there because is not handled by global
requirements.
Remove the separate requirement file for bandit, because
bandit has been part of test-requirements.txt in the last 3 years.
There is noneed for a separate requirements file anymore.
Even more, the bandit tox environment could be probably removed.
- synchronize the requirements for sphinx and jsonschema with the
current values from the requirements repository to make
the requirements-check job happy.
Jobs:
- temporarily disable the scenario-py3 job until a new stestr
(>2.3.1) is tagged.
Change-Id: Ief8e392fcd2d66a73593abcfda06fc7dbe2e53a6
This goal is to implement the process set out in the 2018-10-24 Python
Update Process TC resolution[1], for the Train cycle to ensure unit
testing is in place for all of the Tested Runtimes for Train[2].
In practice, this generally means adding unit tests for Python 3.7 and dropping
unit tests for Python 3.5. Using the Zuul template for Train will ensure that
all projects that support Python3 will be tested against the agreed runtime
versions, and make it easier to update them in future.
[1]https://governance.openstack.org/tc/resolutions/20181024-python-update-process.html
[2]https://governance.openstack.org/tc/reference/runtimes/train.html
Change-Id: If66a364be10271882629e0b278c8729172ff47bd
Depends-On: https://review.opendev.org/#/c/641878/
Sahara fails to connect and operate on remote machines
because the output from Subprocess on python 3 are bytes
and that breaks follow up actions.
Change-Id: Id55e6c06d3b6ead18501a0e2146af37bf493881d
So far grenade has been testing a queens->rocky upgrade.
Implement the grenade code required to upgrade to the current
master. The plugin code installs the split plugins, which
need to be listed in the PROJECTS variable in order to be cloned.
Also, don't deploy sahara-all even when deploying rocky
(it was already deprecated back then).
Finally, deploying sahara-api using wsgi has been the default
for a while and for sure when the upgrade starts from rocky
there is no need to disable it.
The grenade test should be stable enough again, so re-enable it
in both the check and the gate queue.
Change-Id: I000aae6c093c32ab1c3505448e2b9ec52b0529a2
Run also: the API v2 scenario and tempest tests on both the check
and the gate queue.
Remove the list of plugins from required-project, as it was added
to the definition of the job in sahara-tests.git.
Finally, make sure that the base buildimages job depend on the
sahara repository and that it uses the sahara source directory
as working directory.
Change-Id: I97a302e253516cdd827c522178fca5fb5590f00c
Since plugins are not part of Sahara core anymore, loading plugins
like we currently do fails when plugins are not installed.
Currently we check the list of loaded plugins by checking the CONF
file plugins session. To fix that, we are changing to check the list
of loaded plugins on the PluginManager variable loaded_plugins, this
way we can instead of failing to start sahara if a desired plugin
is not installed, we can warn that the plugin was not loaded and
continue the application.
Change-Id: Iaae3a75cd75b06e94bc4492e5dc654a6281fdff4
On the effort to make Sahara more user and operators friendly
we are splitting the plugins from Sahara core.
The main goal of this change is to facilitate installation,
maintainance and upgrade of plugins. With the plugins outside
the main Sahara code, operators will be able to install a subset
of plugins, as well as upgrade to newer versions of the plugins
without having to wait for a new version of OpenStack to be
released. As well, it aims to facilitate new contributors to
develop and maintain their own plugins.
Sahara Spec: https://specs.openstack.org/openstack/sahara-specs/specs/rocky/plugins-outside-sahara-core.html
Change-Id: I7ed0945fd82e37daaf6b29f947d3dba06db9d158
Use openstack-lower-constraints-jobs template.
Remove jobs that are part of the templates.
Remove post job, this is not checked by anybody. The current job is
setup as check job and compares to last change, so no need for a post
job - especially for a post job that nobody checks.
Change-Id: I4fefd5b29c1b16b886c72fc42fbedc07d82397c4
It should have been done in the previous commit, will be squashed
with the main import change when backporting to the older branches.
Change-Id: Icda0eb2f0b001f4468ba86af65b8c5c12fbaebab
While it would have been better to directly use a native Zuul v3 job,
the work towards a common grenade job seems to be stalled.
Import the job locally and fix some issues:
- make sure that the heat_tempest_plugin is loaded correctly,
so that the heat upgrade tests work;
- bump the starting point from stable/ocata (!) to stable/queens;
it will be changed to stable/rocky when grenade supports it;
will require additional fixes due to the standalone->uwsgi change.
- import lib/apache so that wsgi deployment works.
Story: 2001686
Task: 24517
Change-Id: Ia8de2b8286287355e8e9d3f702027aa282ed8282
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: Ibb49209b4c8923a51c53ebaf0fdddb10eed8addf
Story: #2002586
Task: #24332
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: Ic482013bf68ab2f21cdb6c1a4a5c4d6ee5b05788
Story: #2002586
Task: #24332
Complete the switch to wsgi and only use it from now on.
The default won't be changed for old branches (i.e. this change
should not be backported).
Story: 2001991
Task: 19622
Change-Id: Ia23083d0ec7c17a84e0bb4bc5db970cbfe57882a
Create a tox environment for running the unit tests against the lower
bounds of the dependencies.
Create a lower-constraints.txt to be used to enforce the lower bounds
in those tests.
Add openstack-tox-lower-constraints job to the zuul configuration.
See http://lists.openstack.org/pipermail/openstack-dev/2018-March/128352.html
for more details.
Change-Id: I3a1d395b43e77010bf44ba71f5bcf146c01e0098
Depends-On: https://review.openstack.org/555034
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
It defines buildimages/CLI jobs, and reuses the global pylint job
and few jobs from sahara-tests (scenario, tempest), mimicking
the existing definitions of the legacy jobs.
Still missing: grenade (there is no common grenade job yet at this
point).
Change-Id: Ibb57e216410afeef4d55d8ba2576aaacfa2f8c1a