This is step 1 in promoting the openafs deb packages to the
openstack-ci PPA. It should grab the debs from the gate build and
sign the .changes file with our key.
This is intentionally not uploading yet as we just want to test the
secret import and signing path before we add the key and permissions
to the upstream PPA.
Change-Id: Idd91818093588113b84c1d91b4895df589aa7912
This imports the latest debian/* from the upstream openafs packages,
and builds source packages meant for upload to the PPA we use for
openafs.
Over the years we have found that maintaining our own PPA for this is
useful. We have hit bugs that require immediate patches to be applied
and rolled out to production, and having a private build facilitates
this. Generally we hope to have no delta to the upstream packaging,
which is currently the case.
Currently we have a fairly manual process to produce and upload these
debs (once there, the source is obviously available). This allows us
to keep a little clearer view of what we've changed or are working on.
This doesn't publish anything, yet. We'll work on that after this;
the idea is that the publishing job will consume the artifacts this
returns.
Change-Id: I07780595331da29af9f72185cbb3499210e89c19
The promote job is failing with "... openafs/centos8-stream' must be
an existing dir". We probably don't need both 8 and 8-stream now, but
let's just get this working first.
Change-Id: I142786153efb37b19e9994c49f16636bd26c4376
We had to workaround this repo not existing when we first spun up wheel
builds for centos 9 stream. But the repo appears to exist now so use the
official production stuff rather than the test builds.
Change-Id: I85cf1c29d501817254ddc54ef02bd75b848ed942
As per the lates testing runtime the minimum
python version and distro we are using is py38 and ubuntu focal.
So moving lower constraints job to those for testing the
lower bound of defined testing runtime.
Change-Id: Ifbffa10ba2346959869eb819162453f64e1a0540
puppet-openstackci repo is retired now
- I46ccab87f063c51dd3236757dbb0567738803fae
so removing it from job definition to fix the
existing zuul config error.
------------
Unknown projects: opendev/puppet-openstackci
The error appears in the following job stanza:
job:
name: legacy-puppet-openstack-infra-spec-helper-unit
parent: legacy-base
run: playbooks/legacy/puppet-openstack-infra-spec-helper-unit/run.yaml
timeout: 3600
required-projects:
- opendev/puppet-openstackci
in "openstack/openstack-zuul-jobs/zuul.d/zuul-legacy-jobs.yaml@master", line 415, column 3
-------
Change-Id: I1032bcd2bcff0b499431686b1f8238ac43a2bf81
Capping <=6.0 never made sense anyway, also with ansible-lint==6.0.0
things are breaking now because it requires newer ansible.
Signed-off-by: Dr. Jens Harbott <harbott@osism.tech>
Change-Id: Ifb4ab923fe438c22f52b5a9099bbd9b82cba7138
Place the arm64 job templates alongside the other release-specific
templates.
Change-Id: Id1a894f8c7ab9b031c15e89d96b90d642f61d6d6
Signed-off-by: Stephen Finucane <stephenfin@redhat.com>
We switched to using release-specific python3 job templates (e.g.
openstack-python3-ussuri-jobs) after the Train release. This is
generally a good thing, but it has caused slight issues for projects
using the independent release model. These projects don't get a new
stable branch each release, nor do they receive bot-proposed 'zuul.yaml'
changes. This means there are a growing number of projects still using
the checks from older releases [1][2][3][4][5]. This will likely only
continue to grow without intervention.
While these projects are independent, the HEAD of master must be
compatible with the Python 3 versions supported in the current release.
As such, master should always be running again openstack-python3-X-jobs,
where X is the current release. Reworking the bot to do these proposals
for every independent project seems silly and unnecessary, so instead
add a new openstack-python3-jobs template which will always duplicate
the openstack-python3-X-jobs template. Only projects using the
independent release model should use this and this is called out in the
help text for the template.
Note that only openstack-python3-jobs is added currently. We may wish to
add the full complement of jobs, such as openstack-python3-jobs-horizon.
This can be done in a follow-up.
[1] https://codesearch.opendev.org/?q=openstack-python3-ussuri-jobs
[2] https://codesearch.opendev.org/?q=openstack-python3-victoria-jobs
[3] https://codesearch.opendev.org/?q=openstack-python3-wallaby-jobs
[4] https://codesearch.opendev.org/?q=openstack-python3-xena-jobs
[5] https://codesearch.opendev.org/?q=openstack-python3-yoga-jobs
Change-Id: I7acf7485f2a531035b37064ed760f7f29689e8e0
Signed-off-by: Stephen Finucane <stephenfin@redhat.com>
Use Fedora 35 nodeset until ubuntu-focal gets python3.10 package or
until we have ubuntu 22.04
Tests on arm64 arch are not supported at the moment.
Change-Id: I685563200ec342363848b713854c34a86dfb5fd0
TC has defined the python testing runtime[1] and this
commit defines the job template to be used for testing the
defined testing runtime for Zed release[1].
This also defines openstack-python3-zed-jobs-arm64 template
which is needed to continue the arms64 testing as n-v
for many projects like Nova, Cinder, Heat etc.
[1] https://governance.openstack.org/tc/reference/runtimes/zed.html
Change-Id: I84e5b758b087eac0fe59b4683cbc1ab86535b77b
As noted inline, platforms are starting to decide to deprecate
virtualenv for "python3 -m venv". Put in logic to use venv in our
Python 3 paths.
Change-Id: I46778642647d7be995d476fb567a9943cae66b8f
Make sure the pip in the venv is upgraded past the system-version so
it can install all the latest requirements.
Change-Id: I601aca1507d16912e08ee9aba8842bc205ea2a91
This old openstack package brings in centos-release-ceph-nautilus
which actually has an incorrect mirrorlist entry in it's .repo file
that tries to point it at the centos-8 repos [1]. When upstream
retired CentOS 8 this stopped responding. Update to Xena (we don't
rely on any of these bits, it's just one or two packages we need
bindep to install for the wheel builds).
[1] https://bugzilla.redhat.com/show_bug.cgi?id=2051792
Change-Id: Ice106cfee23c514a5e5716d4368af9f62360e2f7
Older ansible-lint has an uncapped dep on 'rich' and newer rich breaks
ansible-lint. New ansible-lint has addressed this. We update
ansible-lint to get those fixes.
This adds task names to a number of tasks to correct a linting error.
Change-Id: I38284fef54213e0fceb1b348d5839129cc15148e
FIPS needs to be enabled before test-setup is run, as enabling
FIPS requires the node to be rebooted, test-setup needs to run and
setup the environment after the reboot.
Updating openstack-tox to inherit from tox-fips and setting
enable-fips as false.
Depends-On: https://review.opendev.org/c/zuul/zuul-jobs/+/816385
Change-Id: If84552b6edf22bae6da95a24d0d010901964f981
TC has updated the Yoga testing runtime by making
the python3.8 and python3.9 as python version to tests
- https://governance.openstack.org/tc/reference/runtimes/yoga.html
Updating the job template to reflect the change.
Change-Id: Ia0bd0c09dd0c76e7940f497f42075691b3ac758d
The swift team want to translate docs into other language.
For docs translation in zanata, I add swift to DOC_TARGETS
Change-Id: I0d9f46d576edf10117d73526505d1a59b40886dc
All the project that had periodic-stable-jobs template set in their
stable/ocata branch have transitioned to End of Life, and their
branches were deleted around end of August [1]. So this patch removes
stable/ocata from the template as it is not needed anymore.
[1] https://zuul.opendev.org/t/openstack/builds?branch=stable%2Focata&pipeline=periodic-stable
Change-Id: I49ebc52f1f8fa553c9b22ac59594a9babb319df8
This patch removes legacy-neutron-dsvm-api job definition
It seems that this job was used only in the Neutron stable/Ocata branch
which is going to be EOL with [1].
In the stable/Pike branch Neutron is using only
"legacy-neutron-dsvm-api-pecan" job which isn't removed by that patch.
It also removes networking-midonet jobs:
* periodic-tempest-dsvm-networking-midonet-aio-ml2-full-ocata
* periodic-tempest-dsvm-networking-midonet-aio-v2-full-ocata
As those jobs were also used only in Ocata branch which is EOL in
networking-midonet already.
[1] https://review.opendev.org/c/openstack/releases/+/790904
Change-Id: I7b9e6cb20d7b8d8d1dff9b8bee2c652df743b2ba
The lower-constraints is supposed to test the oldest version of the
dependencies supposedly supported by a library or service. It doesn't
make sense to be running these on the newest version of Python supported
by OpenStack. Start running lower-constraints on ubuntu-bionic nodes
rather than ubuntu-focal. When we bump our minimum Python version to
e.g. 3.8, we can change this to ubuntu-focal (assuming anyone is still
working with lower-constraints by then).
Change-Id: Icaa4d8e03915d90b542b989ecb62a513125f2642
Signed-off-by: Stephen Finucane <stephenfin@redhat.com>
As per TC resolution on updating the python version for testing,
this commit defines the job template to be used for testing the
defined testing runtime for Yoga release[1].
This also defines openstack-python3-yoga-jobs-arm64 template
which is needed to continue the arms64 testing as n-v
for many projects like Nova, Cinder, Heat etc.
[1] https://governance.openstack.org/tc/reference/runtimes/yoga.html
Change-Id: Ibf0413f556424f2398bb49fd61ecc5f46b7f0b37
neutron-lbaas is retired now and we can
remove it from zuul jobs. It also retire django_openstack_auth
in this patch to unblock the gate.
`django_openstack_auth`` code was merged into the main horizon
repository during the queens release. This repo is already
deprecated and now we can retire it. This patch removes all
references of ``django_openstack_auth`` as mentioned in [1].
[1] https://docs.openstack.org/project-team-guide/repository.html#retiring-a-repository
Change-Id: I5310983bed6c5b1618b7e131996e09571be9f13d
Ian Wienand