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
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
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
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>
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
Python 3.9 is available on Ubuntu Focal. This enables non-voting
tox py39 jobs for the Wallaby templates.
Change-Id: I142a78a5c06e2ababfca147620ceb4b3a12d5646
This has broken a lot of projects that implicitly assume an Ubuntu
environment in their test setup, e.g. Nova and Neutron. I think that
the we need reapproach this with a previous announcement on the ML and
enough time to prepare the switch.
This reverts commit 31c4a7a18e2bd43d2893563b992c683c95baed6f.
Change-Id: I62f6b6a82bae2bda811c98a295d7fa0c0c9ef2cb
We were including zuul/zuul so that we can lint successfully with the
use of zuul_return. However, we've since stubbed out zuul_return in
projects that need it to avoid needing to pull in zuul itself. Remove
zuul as a required-project as part of this cleanup.
Change-Id: I4ced2726a0bb09a8a2c9763995205cd4d595e3a1
While we don't want to be using bionic across all stable branches, focal
doesn't have py27 available. Use xenial for pre-stein, and bionic for
stein and later.
Change-Id: I206b95ee9240345e91229921b6cf14e13f36d254
Related-Change: I7c597c4aa5aeb3b1bb7987efb4afd0c5c15d86e6
https://review.opendev.org/#/c/738326/ created openstack-tox-docs
job for stein-ussuri branches, but it did not specify pre-run and
run phases required for PDF build.
Repositories which enable PDF build with RSVG support requires
librsvg2-bin even for HTNL build (as rsvg-converter is always
specified in doc/source/conf.py). As a result, the above change
breaks HTML doc build in stein-ussuri branches for such repos.
An example is found at [1] (networking-ovn stable/train branch).
This commit makes openstack-tox-docs stein-ussuri same as
that for the master branch.
[1] https://zuul.opendev.org/t/openstack/build/0cd86df4b6aa4896ba033d68d4357948
Change-Id: I61ed9d13f39e88a433d0db2feb5225a1bec861d2
Focal migration patch [1] introduced the use of fixed ubuntu-bionic
nodeset for openstack-tox-py27 job. This is unnecessary, since the
nodeset is controlled by the parent job, openstack-tox, which has 3
job definitions:
- one with nodeset ubuntu-focal for latest branches (victoria, master)
- one with nodeset ubuntu-bionic for ussuri, train and stein
- one with nodeset ubuntu-xenial for rocky, queens, pike and ocata
Besides, the above mentioned change causes openstack-tox-py27 job
failures in stable/ocata and stable/pike, so should be removed.
[1] I8f4982c0ce8fccefe53eb6cd7f5a97b49854b88c
Change-Id: I7c597c4aa5aeb3b1bb7987efb4afd0c5c15d86e6
This reverts commit 9a491100278eccc40219f51a329c0d0980a3d8a6.
As per the Focal migration work, most of the projects have been fixed
for running the l-c job on Focal[1].
As part of this migration, l-c testing the min version of deps can work
on tested Distro which is Focal in this. If I am installing Nova on Focal
then I will be ineterested to see what all min version of Nova deps can
work in Focal. We can debate on this if we need to test on any older distro
which as per supported python or any other distro and accordingly we can
test the l-c job accordingly. But for this in middle of migration we should
keep it tested on Focal compatible.
Cinder and Keystone projects are two main project failing on l-c, let's
keep running their l-c jobs in Bionic
- cinder: https://review.opendev.org/#/c/751118/
- keystone: https://review.opendev.org/#/c/751122/
[1] http://lists.openstack.org/pipermail/openstack-discuss/2020-September/017155.html
Change-Id: I34ef635d1987bde03fe5944f511dfe7ec1fb741f
We've used bionic for py36 testing, but that's not an official distro
for Victoria. This switches those jobs to centos-8 where it is, which
also has py36 as its default runtime.
Change-Id: I6ad8c6669c2fa3cbdfcaa37f4a159330699f089d
Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>
The lower-constraints job is to test our minimum values. Since py3.6 is
our minimum runtime, these jobs should run there rather than the latest
and greatest. This updates the job definition to use bionic nodes.
Change-Id: Ia9beee908cbb4865cecc07c6c7384e1cb6e76bde
Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>
As per victoria cycle testing runtime and community goal[1]
we need to migrate upstream CI/CD to Ubuntu Focal(20.04).
This commit migrates:
- openstack-tox-functional & openstack-tox-functional-with-sudo to
ubuntu focal for victoria onwards and bionic from stable/stein till
stable/ussuri and xenial till stable/rocky on xenial.
- openstack-tox-functional-py37 and openstack-tox-functional-py38
to ubuntu focal for victoria onwards and bionic till stable/ussuri
- openstack-tox-py36 will keep running on Ubuntu Bionic as Ubuntu Focal
does not have python 3.6
[1] https://governance.openstack.org/tc/goals/selected/victoria/migrate-ci-cd-jobs-to-ubuntu-focal.html
Change-Id: Ib98d7456529eeeaa10091f17610a646e28ff6f13
As per victoria cycle testing runtime and community goal[1]
we need to migrate upstream CI/CD to Ubuntu Focal(20.04).
openstack-tox-cover jobs is migrated to ubuntu focal for victoria
onwards and from stable/stein till stable/ussuri it will keep running
on ubuntu bionic and till stable/rocky it will run on xenial.
[1] https://governance.openstack.org/tc/goals/selected/victoria/migrate-ci-cd-jobs-to-ubuntu-focal.html
Change-Id: Id93b02d26b7fe23a23cc73040f688c44258cd425
As per victoria cycle testing runtime and community goal[1]
we need to migrate upstream CI/CD to Ubuntu Focal(20.04).
This commit migrates:
- openstack-tox-py38 to ubuntu focal for victoria
onwards and till stable/ussuri they will keep running on ubuntu bionic.
- pin openstack-tox-py27 on Ubuntu Bionic as Ubuntu Focal does not have python 2.7
[1] https://governance.openstack.org/tc/goals/selected/victoria/migrate-ci-cd-jobs-to-ubuntu-focal.html
Change-Id: I8f4982c0ce8fccefe53eb6cd7f5a97b49854b88c
Some validation jobs in some repos need to invoke tox to run their
specific validations. Tox is being installed already, but it does not
get installed into somewhere on the path. So even though the validate
job gets run via tox, tox is later not found by other places that are
not aware of the venv specific path.
This sets the ensure_global_symlinks variable used by the ensure_tox
role so that the existing tox installation also puts a symlink where tox
can be called globally.
Change-Id: I29d3d7e5b967e1ebec290e3ef00f1c65d1464f9e
Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>
This run openstack-python3-victoria-jobs template with arm64
nodeset.
This template currently runs only a non-voting job
`openstack-tox-py38-arm64`.
Change-Id: If2259fdad175456432a46b9d859ddbd484d81f18
Task: #40398
As per victoria cycle testing runtime and community goal[1]
we need to migrate upstream CI/CD to Ubuntu Focal(20.04).
openstack-tox jobs is migrated to ubuntu focal for victoria
onwards and till stable/ussuri it will keep running on
ubuntu bionic.
[1] https://governance.openstack.org/tc/goals/selected/victoria/migrate-ci-cd-jobs-to-ubuntu-focal.html
Change-Id: I4e26afc38f396f7adf92b6a87ba0e1d73cace186
Change https://review.opendev.org/737995 failed the promote job
openafs-rpm-package-build-promote since the gate job was not run.
Add a files sections, so that the promote job is triggered when the gate
job is.
Change-Id: I2f45d822d1f1301c406799f5dd7a4a1a44f26f0c
We should not be using this on master. Also update it to pin to
python2 to get ready for zuul-jobs changing the default for
sphinx to python3.
Update descriptions to make clear that rocky was the last release
this is supported.
Change-Id: Ib896713623f58a8164d1a2e5f49dc5d316e292b9
As the zuul manual says
If a child job inherits from a parent which defines a pre and post
playbook, then the pre and post playbooks it inherits from the
parent job will run only with the roles that were defined on the
parent.
This is to stop role inheritance altering the parent job. So include
the system-config roles here.
Change-Id: I9e5c0d128e5669e5354c5568bdbc00a3aa27e95b
The extant roles are not really right. They run in periodic and poll
tarballs to see if they should build anything. They are not gate
tested. I do not know why I did it like this; but it was a long time
ago.
We should have roles that build in the check gate, and upload only
when the client version changes.
Additionally, I found that the upstream .srpm we were building from is
not quite right; it won't build on ARM64 for example due to the way
it's autoconf machinery has been generated. The best way is to build
your own srpm from the upstream source using the method linked in this
change.
This builds and publishes artifacts for centos7 x86 and centos8
arm64/x86. A follow-on will publish these.
Change-Id: Iefb01ba48a457388bb5412ddad3d7dafb00d620c