Use pyenv flag for the ensure-python role since python3.12 isn't
available yet as distro pkg on bookworm.
Change-Id: If42cb167c3395e530e3dcd0090bbca86023ac738
We're removing CentOS 7 test nodes from OpenDev and before we can do
that we need to clean up the supporting infrastructure for things like
wheel caching/mirroring which in turn depends on openafs packaging.
Enough time has passed since we announced the CentOS 7 nodes would be
removed that we should be good to start dropping this supporting
infrastructure. Go ahead and make that happen.
Depends-On: https://review.opendev.org/c/openstack/project-config/+/912283
Change-Id: I5c56e0f081b4a4720ca59c8d2b59621fcaaad39d
These tripleo projects were removed from zuul entirely so it is no
longer valid to have them listed as required projects in zuul jobs. This
cleanup also points out that we can probably clean up the entire
legacy-dsvm-* job structure at this point.
Change-Id: I0e3e43cc0525871b39cc1b85c955bcedddfbe0cf
Tox was pinned < version 4 for all stable branches <=zed.
With new branch namespace, those stable branches moving to
unmaintained/* name[1] and endup using the latest tox version
and fail[2]. To fix that, we need to extend the tox pin for
those unmaintianed branches also.
Currently only unmaintained/yoga is proposed but soon or in
future all branches from victoria to zed are moving to
unmaintained/ so pinning tox for those branches also.
[1] https://review.opendev.org/q/topic:%22create-yoga%22
[2] https://zuul.opendev.org/t/openstack/build/201ecdc067e646868c4f17374093f328
Change-Id: I2a977fa9c57e540ded4cc5017283302106f5c807
There are three job definitions here for testing
neutron with the master branches of other projects,
specifically neutron-lib, oslo, and ovsdbapp. As
neutron is no longer testing py310 in its master
gate, create py311 versions of these jobs so we
can move forward.
Also changed the periodic jobs here to start using
the py311 versions.
Change-Id: I28e1d41ebd36fbbe9ed3e4c18dd9604a906af043
Python regexes are deprecated in Zuul, so update the use of regexes
in branch matchers with re2-compatible syntax.
Change-Id: I2216976a9c040cdf1d324f90831a543f7cf4a15d
Nodepool now requires Python 3.11 and so cannot be installed with
the default Python on our default nodeset. Specify a debian-bookworm
nodeset where this version of Python is the default.
Change-Id: I961430b678c3d126a2808320a8529d8649d879ac
Python3.11 is default in Debian 12 and which is going to be
mandatory testing in future cycle. It is good to test it
as non voting in this cycle so that projects will get time
to fix the things in advance.
Change-Id: I8c74a3f21b8696389d692c7b0706cfe6f43120f8
Projects ocata branches have transitioned to End of Life, which means
that all ocata related branch filters and unnecessary definitions can
be removed.
Change-Id: I6bae6ce07c58855379db7afd9394b94de3781fee
Some projects want to include python3.11 in their testing, provide a
generic job for that like we have for older python versions.
Change-Id: I725b94bee6601a81b5e64db204bf3488674eff9d
Increase the timeout for building a snap to 60 minutes; with some
of the transient changes in the Python dependency chain the snaps
have to build quite a few more native extensions, pushing out the
build time.
Change-Id: Icd7f2e10522c2cf69107db74823bf8b767a9e53d
Changes to the normalize_acl.py script should be self-testing so
that we don't break the project-config-gerrit job.
Change-Id: Ib42ee415d39f0239a8ea62c9c3d39b3f215a9ae4
Since Zuul 4.7.0:
> The following attributes are now ignored:
>
> * The ``report-build-page`` tenant configuration setting.
> * The ``success-url`` job attribute.
> * The ``failure-url`` job attribute.
Remove `success-url` from all jobs.
Change-Id: I1379221d47edefff716875d801bedf8eee067314
Stable branches of some projects (Glance, for instance) use Python2.7
for their functional tests. Pre-install Python2 packages for these
stable branches.
Change-Id: Id629fb84ab64db136b12f6e36dfd7aed1c593cd6
Recently openstack-tox-py310-with-oslo-master jobs started to fail
with "No package matching 'python' is available", due to that [1]
dropped py2 from nodepool images, and the base job's parent is
openstack-tox-py27.
[1]: https://review.opendev.org/c/openstack/project-config/+/872476
Change-Id: If66af5320d9a208035d9d1ea219eae7d87a31072
As noted inline, we dropped the install from the base images. This
should pre-install python2/-dev to return us to about the same state,
but just for the legacy jobs.
Change-Id: Ia8cf6911cb48dfbef59fcf890d4b29d162dc11ad
There are two problems we need to solve when enabling FIPS for
multinode Ubuntu jobs.
1. Ubuntu nodes require a subscription to be activated with a
subscription key that is stored as a secret in project-config.
2. Because enabling FIPS requires a reboot, we need to execute the
enable-fips playbook before the multinode playbook. If not,
resources set up by the multinode playbook may not survive the
reboot.
To solve these problems, we have created a new base job for
OpenStack multinode jobs. (openstack-multinode-fips). We expect
to use this job as the base job for OpenStack multinode jobs
instead of the multinode job in zuul-jobs.
The openstack-multinode-fips inherits from openstack-fips, which
is a job defined in project-config that access the UA subscription
key and activates the UA subscription. This solves problem #1.
It then executes the enable-fips and multinode playbooks
(FIPS first!), which in turn, invoke the enable-fips and multinode
roles in zuul-jobs. This solves problem #2.
This has the unfortunate result of having to duplicate the logic
of the multinode/pre.yaml playbook in zuul-jobs here in
openstack-zuul-jobs instead, but I can't see a way around that.
Note that unless the variable enable_fips is defined to be true
in the job, all the FIPS logic is essentially a no-op.
If enable_fips is set to True, then jobs will also need to specify
nslookup_target for the post-reboot-tasks role invoked by the
enable_fips role.
Depends-On: I8a88d6a9bcf5725986b00b063e03686d3225b48e
Change-Id: I080df90af850088893976c8649aa528638c6f373
tox4 need changes in tox.ini file to be compatible with it
and while fixes are merged in master and backported to stable
(if project decide to backport) let's cap the stable branch
testing to tox<4.
This only pin for jobs running for stable branches <=stable/zed.
Change-Id: Id468500746bc5c0986ec3334bfdafc24eeaba2f8
As per 2023.1 testing runtime[1], we need to move gate
test jobs on Ubuntu Jammy (22.04).
OpenStack tox base jobs are migrated to ubuntu jammy for
2023.1 onwards and they will continue running on Focal
until stable/zed.
[1] https://governance.openstack.org/tc/reference/runtimes/2023.1.html
Change-Id: If9bab60107ea2f049f0940766cf44ce3ebb002ee
The build-openstack-puppet-tarball job consistently fails since
the default node set was switched from Focal to Jammy. This change
pins the node set back to Focal until we fix the current issue.
Change-Id: Ib1a55d624c72aa773ab03b736efed0699f35e946
The following py39 based jobs has been changed to py310 based in these
templates:
- periodic-jobs-with-neutron-lib-master
- periodic-jobs-with-oslo-master
- periodic-jobs-with-ovsdbapp-master
Change-Id: I96023fb323647465dacc450567d4a6adf6f59314
Since ocata and pike have transitioned to EOL, these filters are not
needed anymore and can be deleted.
This patch also removes some job definition which were only used for
ocata and pike branches.
Change-Id: I69ebf0ae122220ae8c88310094468aedb3f4a660
When adding the latest py310 jobs the arm64 job was forgotten.
This resolves the zuul config error by adding the job.
Change-Id: I6a691ccdf62db9117e9e26962af1592486c94288
This reverts commit ace49f32d9.
This job calls use-buildset-registry which needs a registry running to
work. We think this is basically as designed;
https://review.opendev.org/#/q/I74c771d048c7a808511864445ed1a124644f661a
adds this to project-config. Since we've decided this is a hard
dependency, revert this change.
Change-Id: Id07f728b8414d29f107ee2d00590d417d20867e5
This job was meant to work by either pulling through the registry for
speculative testing, or for project-config just running on released
images. Make this soft so project-config doens't have to start a
registry.
Change-Id: Icd1b531de30a34780a340ea02209f49eb925de36
This is a job that imports the graphs we have defined in
project-config/grafana to a testing grafana instance, then takes some
screenshots to validate the layout and aid review.
Operation is fairly straight-forward; a grafana container is setup
(see related work in Ibbc2b116d0c496655a7ce6bb6971e8270ac32647) and
grafyaml is used to import the dashboards from project-config. We
query the grafana instance to find the dashboards, then use selenium
and a small helper to take screenshots of each.
It pulls graphyaml from the buildset registry as a soft dependency, so
we can also add it as an extra test to the grafyaml repo.
Change-Id: Ice0863d5a180738119d572df1871093a292126be
This job runs on Ubuntu focal in which by default there is no python 3.9
installed.
To install it we need to define "python_version" variable in that job.
Change-Id: I9aee024e2055056a44224f675f786d8633445568
Below master template has been moved to py39 based
testing
- periodic-jobs-with-neutron-lib-master
- periodic-jobs-with-oslo-master
- periodic-jobs-with-ovsdbapp-master
Change-Id: Ic176f01330e680b0dcebf955e219b634c50d55c8
Dr. Jens Harbott